Teradata Viewpoint, which includes 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 enable changes to rule values
Request-Specific Performance Management
Using Teradata Viewpoint Workload Designer portlet, you can define rules according to which workload is managed. The following table describes the categories of Teradata Active System Management (ASM) rules.
Rule Category | Description |
---|---|
Filter | Rejects unwanted logon and query requests before they run. Restricts 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) | Enforces session and query concurrency limits on specific objects. When creating throttle rules, you can do the following:
|
Workload (also called Workload Definitions [WDs]) | Specifies how Vantage handles running queries by specifying parameters for up to 36 workload definitions. In each workload definition, you can specify the following:
|
Event-Based Performance Management
Using Teradata Viewpoint Workload Designer portlet, you can specify filter, throttle, and 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. For example:
Event | Description |
---|---|
Health Condition | Reflects the health of the system, such as a Vantage 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 Vantage is expected to do, such as batch and loads or month-end processing, defined as time periods. |