16.10 - Workload Definition Summary - Teradata Workload Management

Teradata Database Workload Management User Guide

Teradata Workload Management
June 2017
User Guide
Workload Characteristics Required Optional Description
Classification Yes   Which requests should be assigned to the workload.
Throttle   Yes How many requests in this workload can run concurrently.
Priority Yes   The priority assigned to the workload.

Teradata Database with SLES 11 has a hierarchy-based priority management system.

Service Level Goals   Yes Service level goals (SLGs) for workload request performance, defined as either response time or throughput.

For example, queries in the WD-Dashboard workload are expected to complete in 2 seconds, while requests in WD-MktRepts are expected to complete within 1 hour.

Exceptions   Yes Requests that start to execute and then display characteristics unsuitable for the workload, such as high skew or too much CPU processing.
Tactical exceptions and Tactical exception actions are required for Tactical workloads.
Exception Actions   Yes The automatic actions to take when an exception occurs.
Hold Query Responses   Yes Minimum response times for requests. This option provides a greater degree of consistency within a workload, whether the system is busy or lightly loaded.
Virtual Partitions   Yes A collection of workloads. One virtual partition is adequate for most systems. Platforms that support distinct business units or geographic entities may use multiple virtual partitions to keep this work separated. Each virtual partition supports Tactical, SLG tier, and Timeshare workload management methods.