BEGIN/REPLACE/END QUERY LOGGING Statements - Teradata Database

Statement

Purpose

BEGIN QUERY LOGGING

When submitted by a user with EXECUTE privilege on DBQLAccessMacro, this statement enables logging for the named users, accounts, and applications triplet.

Log only a maximum of:

per statement. If logging is to be enabled for more than 100 users, use blocks of BEGIN QUERY LOGGING statements with 100 users each. For active sessions, logging begins when Teradata Database receives the next query.

You can also enable a rule to make sure no logging takes place for a user, account, or application name.

For more information, see “Logging Scenarios” on page 373.

REPLACE QUERY LOGGING

When submitted by a user with EXECUTE privilege on DBQLAccessMacro, this statement enables logging and deletes the existing rule in the DBC.DBQLRuleTbl table if one matches the users, accounts, applications triplet, and then creates a new rule. If no rule exists, the new rule is added to the DBC.DBQLRuleTbl table.

END QUERY LOGGING

When submitted by a user with EXECUTE privilege on DBQLAccessMacro, this statement stops logging for the named users, accounts, or applications. Each END QUERY LOGGING statement should list fewer than 100 users/ 100 accounts for one user/ 100 applications. DBQL calls a routine that commits the data and flushes all the DBQL caches.

Each time you issue an END QUERY LOGGING statement, the system will flush all the rules cache and will flush the DBQL data tables.

You can also flush the DBQL cache using other methods. See “Options for Flushing the DBQL Cache” on page 372.

For more information on END QUERY LOGGING, see “Effects of Dynamically Enabling/Replacing/Disabling Logging on Current Rules” on page 389.