Defining a Ruleset
You must create a TASM ruleset to contain any workload management rules that you create. You can create multiple rule sets, but only one ruleset can active at a time. For instructions on using the Workload Designer portlet, see Teradata Viewpoint User Guide.
In the Ruleset General View:
1 Name the ruleset.
2 Use the default Interval settings.
3 Use the default Blocker settings.
4 Defining Bypass rules is optional, but not recommended for initial implementation.
Note: Database user DBC bypasses all rules by default.
5 Create the needed classification session, filter, and throttle rules within the ruleset to manage your database workload, as shown in the topics that follow.
You can set the following classification parameters for the session, filter or throttle rules you create, to narrow the effects of the rules, unless you want a rule to apply globally.
You can use the sessions tab in a ruleset to set limits on the:
A filter rejects a query before the query starts running. You can apply filters globally or according to classification rules.
For example, you can create a filter that prohibits a specific user (source classification) from running a query with an estimated processing time of longer than 15 minutes (query characteristic classification).
For information on Ruleset Filters, see Teradata Viewpoint User Guide.
A throttle limits the number of concurrent queries in a filter classification. When the throttle limit is reached, additional affected queries go into the delay queue.
You can create throttles to limit concurrency according to throttle classification, for example:
Suggested Custom Throttles
The following example throttles can be useful for most implementations.
Throttle all at 52:
Throttle High, Medium, and Low PG queries with estimated processing time > 1 second: