Mode Logging Option - 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
ft:locale
en-US
ft:lastEdition
2024-10-04
dita:mapPath
pgf1628096104492.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
ujp1472240543947
lifecycle
latest
Product Category
Teradata Vantage™

The following option controls which CPU/IO collection algorithm Teradata uses for this query logging request.

Parameter Logging Behavior
MODE = m The CPU/IO collection algorithm to use for this query logging request, as specified by m. Possible values are:
  • 0 = Use the default value for this release (algorithm 1).
  • 1 = Use the classic algorithm 1 with step adjustments.
  • 2 = Use AMP algorithm 2 (diagnostic only).
  • 3 = Use AMP algorithm 3 (which includes data on aborted and parallel steps).

    This is the default setting for fresh installations for Release 17.00 and later.

If you do not specify MODE, the algorithm is controlled by the DBS Control General field 64 DBQL CPU/IO Collection. For more information, see Teradata Vantage™ - Database Utilities, B035-1102.

To set the algorithm in DBS Control, see Setting DBQL Logging Algorithm.

For SQL Engine 17.00 and later, the default mode for DBQL logging is set to Algorithm 3. Algorithm 3 collects information more accurately than the previous default of Algorithm 1. Algorithm 3 captures data for aborted and parallel steps, step instances for iterative steps, and Algorithm 3 includes additional information and status about step and request execution over Algorithms 1 and 2.

You must have the EXECUTE privilege on DBC.DBQLModeMacro to use this option.