Capturing DBQL Through the Account String - Analytics Database - Teradata Vantage

Database Administration

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-11-03
dita:mapPath
pgf1628096104492.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
ujp1472240543947
lifecycle
latest
Product Category
Teradata Vantageā„¢

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.