Using Logging to Monitor Zones | Teradata Vantage - 17.20 - Using Logging to Monitor Zones - Analytics Database - Teradata Vantage

Teradata Vantage™ - Analytics Database Security Administration - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-03-07
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572

Logging syntax within zones, including BEGIN LOGGING, END LOGGING, BEGIN QUERY LOGGING, REPLACE QUERY LOGGING, END QUERY LOGGING, and SHOW QUERY LOGGING, is unchanged. Logging and query logging privileges within zones are the same as those for non-zone query logging.

Zone DBAs can use zone-level logging to monitor their zones and can use zone-level query logging to monitor the queries of the users in their zones. Non-zone users other than the DBC user cannot enable query logging on objects across all zones unless they have the ZONE OVERRIDE privilege.

The Vantage DBC user has access to all dictionary data in the database without any zone restrictions. If other users from outside a zone need to collect system-wide dictionary data, the DBC user must grant them the ZONE OVERRIDE privilege. The DBC user receives the ZONE OVERRIDE privilege during system initialization and can grant this privilege, without the WITH GRANT OPTION privilege, to other users. This privilege applies to dictionary table and view access only; it does not apply to data table access.

For information about using GRANT ZONE OVERRIDE and REVOKE ZONE OVERRIDE, see Teradata Vantage™ - SQL Data Control Language, B035-1149.