Effects of Dynamically Enabling/Replacing/Disabling Logging on Current Rules
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 |
|
|
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 |
|
|
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. |