Access Logging versus DBQL
Teradata Teradata Discussion Forums Teradata.com Discussion Forum
Visit Teradata.com
Home       Guidelines    Member List
Welcome Guest ( Login | Register )
        


This online forum is for user-to-user discussions of Teradata products, and is not an official customer support channel for Teradata. If you require direct assistance, please contact Teradata support.


Access Logging versus DBQL Expand / Collapse
Author
Message
Posted 6/2/2008 7:30:48 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 6/2/2008 7:49:02 AM
Posts: 1, Visits: 5
Hi,

We have a report that reports on the number of Access Denials and the objects that are trying to be accessed in Access Logging (Result = 'D').

However, we would like to switch Access Logging off and use DBQL only .(we currently use both)

Since the Result, SeqinHash columns isn't in DBQL how have others got around this problem.

Many thanks

tvrprice
Post #11698
Posted 6/2/2008 8:12:34 AM
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: 10/3/2008 7:39:41 AM
Posts: 483, Visits: 213
Hi tvrprice,
what problem do you have in mind?
You just get multiple rows within DBQL as you get multiple rows within AccessLog.

But if the AccessLog is used for security reasons, i'd recommend staying with it. DBQL might miss some denials, but AccessLog won't.
Just reduce the logging down to denials.

Dieter
Post #11700
« Prev Topic | Next Topic »


Reading This Topic Expand / Collapse
Active Users: 0 ( 0 guests, 0 members, 0 anonymous members )
No members currently viewing this topic.


All times are GMT -5:00, Time now is 11:16am

Powered By InstantForum.NET v4.1.4 © 2008
Execution: 0.063. 8 queries. Compression Disabled.