BY user_name - Teradata Database

SQL Data Definition Language Syntax and Examples

Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Product
Teradata Database
Release Number
20.00
Publication Date
June 2025
Content Type
SQL Reference
Publication ID
B035-1144-200K
ft:locale
en-US
ft:lastEdition
2026-09-23
dita:mapPath
mbm1747160743883.ditamap
dita:ditavalPath
jlp1749501702948.ditaval
ft:sourceId
dita
dita:id
mdr1472255012272
lifecycle
latest

The optional list of users to which the logging rules in this BEGIN LOGGING statement apply.

For logging of users authorized privileges by the Teradata system, the user name must be an existing user.

For logging of users authorized privileges in an LDAP directory (that is, AuthorizationSupported=yes in the authentication mechanism):
  • If the user is mapped to a permanent database user object in the directory, specify the mapped database user name.
  • If the user is not mapped to a permanent database user object in the directory, logging is not supported.

Absence of the BY user_name option specifies all users (those already defined to the system as well as any defined in the future while this logging directive is in effect).

If neither BY user_name nor ON keyword object_name are specified, then the specified action is logged for all users and objects throughout the system.