Access logging v/s dbql object table

Database
Enthusiast

Access logging v/s dbql object table

Hi,

I have read that in access logging you ask the database to log who’s doing what on a given object. The information stored is based on the object not the SQL fired or the user who fired it.So my question is why we do this when we have same info in dbql object table.

Tags (2)
2 REPLIES
Teradata Employee

Re: Access logging v/s dbql object table

Access logging is intended for auditing purposes; the access log row must be written before the request can actually be executed. You can choose to log DDL and DCL as well as DML access, and access to macros, functions, and stored procedures. You can also log DENIALS of access.

On the other hand, DBQL is much lower overhead and recommended if there is no audit requirement, e,g. if you want to determine which tables / columns are used most or least.

Enthusiast

Re: Access logging v/s dbql object table

Thanks Fred!!