15.00 - REPLACE QUERY LOGGING Avoids the Problems of Ending an Existing Query Logging Rule Set - Teradata Database

Teradata Database SQL Data Definition Language Detailed Topics

prodname
Teradata Database
vrm_release
15.00
category
Programming Reference
featnum
B035-1184-015K

REPLACE QUERY LOGGING Avoids the Problems of Ending an Existing Query Logging Rule Set

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;

Related Topics

See the following topics for information related to the REPLACE QUERY LOGGING statement.

  • “BEGIN QUERY LOGGING” on page 157
  • “BEGIN QUERY LOGGING” in SQL Data Definition Language Syntax and Examples
  • “END QUERY LOGGING” on page 822
  • “END QUERY LOGGING” in SQL Data Definition Language Syntax and Examples
  • “FLUSH QUERY LOGGING” on page 824
  • “FLUSH QUERY LOGGING” in SQL Data Definition Language Syntax and Examples
  • “REPLACE QUERY LOGGING” in SQL Data Definition Language Syntax and Examples
  • Database Administration