REPLACE QUERY LOGGING Usage Notes - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
ft:locale
en-US
ft:lastEdition
2024-12-11
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

You can use an END QUERY LOGGING request like the following to end all the rules in the DBC.DBQLRuleTbl.

END QUERY LOGGING ON ALL RULES;

However, between the time all the rules have been ended and a new rule has begun with newly specified options, logging does not take place for the specified user, application, or account.

To avoid this problem, the REPLACE QUERY LOGGING statement simply replaces an existing rule using a request like one of the following.

REPLACE QUERY LOGGING WITH options ON user_name ACCOUNT = 'acct_ID'

or

REPLACE QUERY LOGGING WITH options on APPL_NAME=application_name;