Workload Evaluation Order | Teradata Vantage - 17.10 - Workload Evaluation Order - Advanced SQL Engine - Teradata Workload Management

Teradata Vantageā„¢ - Workload Management User Guide

Advanced SQL Engine
Teradata Workload Management
Release Number
Release Date
July 2021
Content Type
User Guide
Publication ID
English (United States)

When TASM classifies a request, it may match more than one workload. To avoid uncertainty as to which workload a request should be assigned to, adjust the workload evaluation order. When multiple workloads could apply to a request, the system always uses the workload closest to the top of the list.

Consider evaluation order carefully. The classification process stops when the request finds a match. In the following scenarios, evaluation order affects results in surprising ways:
  • If you have a workload with a criterion of Not-All-AMPs because you want Tactical requests to be evaluated first, utility work may unexpectedly go in the workload. This is because utility work can sometimes use only some AMPs.
  • If you include a criterion of USER = * early in the evaluation order, all requests would run there, and subsequent workloads would not be considered.
Tip: Configure workload evaluation order so that it starts with criteria that is most specific (such as DBA, BAR, and load utility work) and ends with criteria that is most generic. This ensures that work classifies to the proper workload.