Effects of Dynamically Enabling/Replacing/Disabling Logging on Current Rules - Teradata VantageCloud Lake

Lake - Database Reference

Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
ohi1683672393549.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
ohi1683672393549

When you enable, replace, or disable query logging, the 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.

Action Query for Session Result
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.
End a session that is being logged Cached If a default row is being logged (logging was not only 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 is logged (perhaps in cache if 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 the DBQL logging rule can be applied on the session is re-evaluated on the next query.