Ruleset Basics | Teradata Vantage - 17.00 - Ruleset Basics - Teradata Workload Management

Teradata Vantageā„¢ - Workload Management User Guide

prodname
Advanced SQL Engine
Teradata Workload Management
vrm_release
17.00
created_date
June 2020
category
Administration
User Guide
featnum
B035-1197-170K
Rulesets are the foundation of workload management. Administrators use the Workload Designer portlet to create rules that define how the work submitted to Teradata should behave and under what circumstances. Rulesets control the following database behavior:
  • Which requests are allowed to run
  • How many requests with specific characteristics can run at the same time
  • What priority the requests should run in
  • What Vantage does if a request behaves unexpectedly or uses too many resources
  • How many system resources a request can consume

In a stable environment, one ruleset is all you need. After you create all rules in the main ruleset and activate it and test it, you might try out a new ruleset to see if it is an improvement. To do that, either activate the new ruleset or clone your existing ruleset to preserve original rules and then make changes. In either case, keep the old ruleset definition in case you need to return to it. Only one ruleset can be active at a time. Delete all rulesets you no longer need.

Do not change the ruleset to make periodic setting changes in TASM, for example, changing the ruleset when the system is very busy. TASM state changes accommodate that need with minimal overhead. Ruleset changes involve greater overhead and are appropriate only when you are setting up a new system or tuning an existing one.

New SLES 11 and Teradata Data Warehouse appliances are delivered with the FirstConfig ruleset enabled. FirstConfig has basic throttle rules that ensure that users cannot overrun the system with requests. You will want to create a new ruleset adapted to the specific needs and goals of your business.