Teradata Viewpoint - Analytics Database - Teradata Vantage

Database Introduction

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-09-27
dita:mapPath
gtm1628096154303.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
dsm1472253642401
lifecycle
latest
Product Category
Teradata Vantageā„¢
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:
  • Restrict the number of requests simultaneously run against a database object (such as requests made by a user or against a table).
  • Reject requests over the concurrency limit on a state-by-state basis (where state is a set of working values for a rule set).
  • Enforce concurrency limits on FastLoad, MultiLoad, FastExport, and DSA utilities.
  • Apply them to workloads.
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:
  • Include and Exclude conditions or database objects, or both the workload definition and database objects that determine whether a query is assigned to the class.
    You can use wildcard characters (such as "*" and "?") to include all or a group of database objects and then exclude specific ones.
  • Execution priority.
  • Query concurrency limits. Requests over the concurrency limit can be rejected on a state-by-state basis.
  • Conditions that invoke an exception after a query starts running.

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.