﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Teradata Forums / Teradata  / Teradata Database  / Access Logging versus DBQL / Latest Posts</title><generator>InstantForum.NET v4.1.4</generator><description>Teradata Forums</description><link>http://www.teradata.com/teradataforum/</link><webMaster>info@teradata.com</webMaster><lastBuildDate>Wed, 03 Dec 2008 16:17:39 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Access Logging versus DBQL</title><link>http://www.teradata.com/teradataforum/Topic11698-9-1.aspx</link><description>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</description><pubDate>Mon, 02 Jun 2008 08:12:34 GMT</pubDate><dc:creator>dnoeth</dc:creator></item><item><title>Access Logging versus DBQL</title><link>http://www.teradata.com/teradataforum/Topic11698-9-1.aspx</link><description>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 thankstvrprice</description><pubDate>Mon, 02 Jun 2008 07:30:48 GMT</pubDate><dc:creator>TVRPRICE</dc:creator></item></channel></rss>