16.10 - Capturing DBQL Through the Account String - Teradata Database

Teradata Database Administration

Teradata Database
Release Number
April 2018
Content Type
Publication ID
English (United States)
Last Update

Teradata recommends that you specify which requests will be captured through DBQL via the account string. The recommendation is to 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 '$M00ABCD&D&H'.

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.

You cannot log use count information for account strings.