Working Values | Teradata Vantage - Working Values - Analytics Database - Teradata Workload Management

Teradata Vantageā„¢ - Workload Management User Guide - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Workload Management
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-01-27
dita:mapPath
aji1628112479055.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1197
Product Category
Teradata Vantage

Some parameters in rulesets can be changed in different states and some cannot. You can customize system-level attributes, such as filters and throttles, for different states. Different states can have filters and throttles enabled or disabled or they can have different throttles limits.

You can also customize some workload characteristics for different states. To understand what you can change about a workload when a state change occurs and what you cannot change, consider that workloads contain these two types of properties:
  • Fixed attributes: The details that define the workload, which include the following items:
    • Classification criteria
    • Exception definitions and actions
    • Position (or tier) in the priority hierarchy
    • Evaluation order of the workload
  • Working values: The variables that are part of the Workload Definition, which include the following items:
    • Workload or virtual partition share percent values
    • Workload throttles
    • Exception enabling or disabling
    • Service Level Goals
    • Minimum response time (called Hold Query Responses in Viewpoint Workload Designer)
The following workload working values may vary based on the planned environment in effect:
  • Service Level Goals
  • Hold Query Responses
  • Exception enabling or disabling
  • Workload management method priority values (workload distribution or timeshare access levels)
The following settings may vary based on the state in effect:
  • Session controls
  • Workload throttles
  • System throttles
  • Resource limits
  • Filters
  • Query session limits
  • Utility limits

Often, workloads do not keep the same level of importance throughout the day, week, month, or year. A load workload may be more important at night, and a request workload may be more important during the day. Also, when the system is degraded, it may be more important to complete tactical workloads than strategic workloads.