Rules Validation | Teradata Vantage - 17.00 - 17.05 - Rules Validation - 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

The following table lists the rules DBQL validates when DBQL logging begins. DBQL checks against the application name, user name, and account string to validate rules.

IF a… THEN DBQL …
user logs on to start a session checks the username, account string, application name, and zone ID (in secure-zoned systems) in the rules cache and also looks for this in the dictionary table.
match is found in the rules cache logs according to any options in the rules table.
match is not found in the rules cache searches for a matching user or account in the Data Dictionary.
match is found in the Data Dictionary creates an entry in the rules cache and logs according to any options in the rules table.
match is not found in the Data Dictionary creates a “do not log” rule in the rules cache but does not perform logging.
“WITH NONE” rule is found creates a “do not log” rule in the rules cache but does not perform logging.
If the account string of a session is changed via the SET SESSION ACCOUNT statement, the system ensures that any rules associated with the user and account string applies when the next query is issued from that session.