Working with Teradata access logging
The Teradata product provides an access logging feature that generates log entries when Teradata checks the specific security privileges of various users on one or more databases. Although access logging provides considerable and meaningful security information, this feature significantly increases processor usage and can degrade system performance.
If you need to improve system performance, evaluate the checking privilege rules that you defined for access logging. Then, terminate any unnecessary rules by defining END LOGGING statements.
For the best performance, turn off all access logging. Drop the Teradata DBC.AccLogRules macro and then force a trusted parallel application (TPA) reset to stop access logging completely.
See the Teradata documentation for more information.