17.00 - 17.05 - Effects of Dynamically Enabling/Replacing/Disabling Logging on Current Rules - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Database Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.00
17.05
Published
June 2020
Language
English (United States)
Last Update
2021-01-22
dita:mapPath
rgu1556127906220.ditamap
dita:ditavalPath
lze1555437562152.ditaval

When you enable, replace, or disable query logging, the currently running query is not affected, but all subsequent queries take on new rule changes.

The following table describes the DBQL behavior as a result of a change to an active session.

IF you… AND a query for that session is already… THEN …
enable logging (submit a BEGIN QUERY LOGGING statement) for an active session in process
  • Data for the current query is not collected.
  • Logging begins with receipt of the next query.
replace an existing rule (submit a REPLACE QUERY LOGGING statement) in process logging begins with receipt of the next query.
abort a session that is being logged cached if a default row is being logged (logging was not just SUMMARY), the AbortFlag is set to T.
disable logging (submit an END QUERY LOGGING statement) for an active session cached
  • One or more DBQL rows are written (but may be incomplete).
  • The current query will be logged (perhaps in cache if it is in flight).
  • All DBQL caches are flushed.
  • Subsequent queries during that session are not logged.
  • All rules caches are flushed.
change a logon account of a user while the user is submitting queries that are under DBQL logging in process whether or not the DBQL logging rule can be applied on the session is re-evaluated on the next query.