A workload is a group of queries that share characteristics so that a set of workload management controls can be applied to the group. A workload has working values and defining characteristics that are evaluated during the classification phase of system management. High-quality workload management can improve response times and provide more consistent response times for critical work. The IWM system has no options for the SLG Tiers workload management method or virtual partitions.
The following requests are examples of workloads:
- Batch jobs further subdivided by region or organization for reporting
- Weekly or monthly reports that follow the calendar or a regular schedule
- Jobs that are always critical whenever they occur
The Workloads view on the ruleset toolbar lists workload names, method or type, throttle limits, group throttles, and enabled status. For each workload, you can specify one or more of the following:
- Classification
- Criteria that determine if a query is assigned to the workload
- Throttles
- Limits on the number of concurrent active queries that can run in a workload
- Service Level Goals
- Goals for workload query performance in terms of response time or throughput
- Hold Query Responses
- For Teradata Database 15.10 SLES 11, enforces a delay so query responses are not returned sooner than an amount of time you specify
- Exceptions
- Thresholds and actions to take if a query exceeds exception criteria while executing
The following are the default workloads.
| Default Workload | Description |
|---|---|
| H-WD | Uses $H classification criteria, which has been deprecated by SLES 11. |
| L-WD | Uses $L classification criteria, which has been deprecated by SLES 11. |
| M-WD | Uses $M classification criteria, which has been deprecated by SLES 11. |
| T-WD | Uses $R classification criteria, which has been deprecated by SLES 11. |
| WD-Default | Contains queries not classified into a specific workload. This workload cannot be deleted or disabled. |
| WD-MapsMover | (Teradata Database 16.10 and later) Use in conjunction with the Maps Mover operations. Supports table relocations across maps. This workload can be deleted or disabled, but it cannot be cloned or edited. This workload can be moved to any timeshare access method. |