The Process of Merging Workloads - Teradata Workload Analyzer

Teradata Workload Analyzer User Guide

Product
Teradata Workload Analyzer
Release Number
16.20
Published
October 2018
Language
English (United States)
Last Update
2018-10-12
dita:mapPath
sef1527114222310.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2514
lifecycle
previous
Product Category
Teradata Tools and Utilities
The process of merging workloads involves the following:
  1. Merge the workload classifications of different criteria and remove any duplicate classifications.
  2. Assign the appropriate performance AG mapping for the resulting workload.
  3. Calculate or recalculate the service level goals for the merged workload (which can be accepted or modified service level goals from the SLG Graph window.)
  4. Merge the workload classifications.

The merging process performs a union of classifications of all workloads selected for the merge process. Any duplicates of the workload classifications values are removed.

Currently, in workload classification, all clusters can be either included or excluded. The same rule is used for merging workloads. If the merge process comes across both exclude/include classification criteria, it would unionize all the classification criteria and assign exclude/include based on the criteria in the selected workloads. See the following figure for an example of merging workloads together.

Example of Two Workloads Merging

The following workloads and classifications cannot be merged:
  • A workload with AMP Limits classification cannot be merged with a workload with Final Row Count classification.
  • A workload with Utility Type classification cannot be merged with a workload with Estimated Row Count, Estimated Processing Time, AMP Limits, or Object Type classifications.