Considerations for Rulesets | Teradata Vantage - Considerations for Rulesets - Teradata Workload Management - Database Engine 20

Workload Management User Guide - 20.00

Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Product
Database Engine 20
Teradata Workload Management
Release Number
20.00
Published
June 2025
ft:locale
en-US
ft:lastEdition
2025-11-20
dita:mapPath
gew1747088853217.ditamap
dita:ditavalPath
jlp1749501702948.ditaval
dita:id
icm1467243640567
Product Category
Teradata Vantage

For normal operating procedures, Teradata recommends that sites rely on a single ruleset. However, you can create varied states to define how TASM allocates resources during different times of the day, different days of the month, or when external conditions or system-wide events degrade system performance. Moving from one state to another, due to planned or unplanned circumstances, results in an automatic change in the workload management settings. Only one state in one ruleset can be in effect at a time. For more information on states, see States and Events Overview.

Within a ruleset, each rule (specifically, session control, filter, system throttle, or Workload Definition) is divided into fixed attributes and working values. Fixed attributes do not change when the system state changes; however, working values for a rule can change to meet the needs of a particular state or planned environment.