Teradata Viewpoint, including the Workload Designer portlet, supports the creation of the following based on business-driven allocations of operating resources:
- Filter rules
- Throttle rules
- Rules that define classes of queries (Workload Definitions [WDs])
- Events to monitor system resources
- States to allow changes to rule values
Request-Specific Performance Management
Teradata Viewpoint Workload Designer portlet lets users define rules according to which workload is managed. The following table describes the three categories of Teradata Active System Management (ASM) rules.
| Rules | Description |
|---|---|
| Filter | Reject unwanted logon and query requests before they are executed. Filters restrict access to specific database objects for some or all types of SQL requests. You can prohibit queries that are estimated to access too many rows, take too long, and perform some types of joins. |
| Throttle (also called concurrency rules) | Enforce session and query concurrency limits on specific objects. When creating throttle rules, you can:
|
| Workload (also called Workload Definitions [WDs]) | Specify how Teradata Database should handle queries while they are executing by specifying parameters for up to 36 separate workload definitions. In each workload definition, you can specify:
|
Event-Based Performance Management
Teradata Viewpoint Workload Designer portlet allows you to specify filter, throttle, and workload rules (WDs) that dynamically adjust their behavior based on system and user-defined events.
An event is any condition or indication that you think is pertinent to workload management.
| Event | Description |
|---|---|
| Health Condition | Reflects the health of the system, such as a Teradata Database component degrading or failing (a node down, for example), or resources below a threshold for some period of time. |
| Planned Environment | Includes the kinds of work Teradata Database is expected to perform, such as batch and loads or month-end processing, defined as time periods. |