Capturing DBQL Through the Account String - Teradata Database

Teradata Database Administration

Teradata Database
Release Number
English (United States)
Last Update
Product Category

Capturing DBQL Through the Account String

In the Teradata Active Enterprise Data Warehouse (EDW), the recommendation is to specify which requests will be captured through DBQL via the account string. Whether you are working in a non-TASM environment or a TASM environment, you should have 10 to 40 different account strings based on various workloads on the system. The recommendation is to characterize the difference between work groups using 4 characters (for example, ABCD). The 4 characters should identify each work group based on workload characteristics, such as business priority and by reporting. Differentiating work groups in the account string allows you to report usage, such as CPU consumption by account string. The recommended account string format for all usage is '$PG$ABCD&S&D&H'.

Note: TASM does not use the performance group constructs in the account string (that is, $PG$).

The advantage to logging DBQL by account string is that it keeps the logging rules to a minimum and alleviates the need to log a DBQL rule every time a user ID is created.

Also the SQL logging needs the Teradata Active EDW to align with existing workload classifications. In other words, each SQL transaction within a given workload type, such as single session tactical, would be logged in a similar manner.

Note: You cannot log use count information for account strings.