 |
 |
Archives of the TeradataForum
Message Posted: Wed, 24 Jul 2002 @ 15:27:25 GMT
Subj: | | Re: Access Logging and changing the log table |
|
From: | | Geoffrey Rommel |
| And, what do you put into AccessLogRights? | |
I assume you mean AccLogRuleTbl. The contents of this table are maintained by the BEGIN LOGGING and END LOGGING statements. See
your friendly documentation. We usually run something like this:
begin logging with text on each all on database X;
But be careful! It's easy to get far too many rows in the log. The above statement is appropriate for a database where your users are
running ad hoc queries and each one could be different, but not for all databases. For instance, if your load jobs perform millions of
single-row inserts, and you need to log them, consider "for first all" or "for first insert".
| |