15.10 - ON object Clause - Teradata Database

Teradata Database SQL Data Definition Language Syntax and Examples

prodname
Teradata Database
vrm_release
15.10
created_date
December 2015
category
Programming Reference
featnum
B035-1144-151K

One or more database objects for which access logging is to be discontinued. You can specify to end logging on up to 20 objects.

If you do not specify the ON keyword object_name option, the system applies the other end logging rules specified elsewhere in the statement to all objects.

Each object in the ON clause must be preceded by the keyword that indicates the object type: DATABASE, FUNCTION, MACRO, PROCEDURE, TABLE, TYPE, USER, or VIEW, followed by the object name.

The ON keyword object_name option does not apply to the CREATE PROFILE, DROP PROFILE, CREATE ROLE, or DROP ROLE operation because profiles and roles are system-level objects with no containing user or database.

DATABASE
For databases, you must specify a qualified object name that includes the name of the containing database or user. For example, database_name.object_name or user_name.object_name.
FUNCTION
For functions, you must specify a qualified object name that includes the name of the containing database or user. For example, database_name. object_name or user_name.object_name.
MACRO
For macros, you must specify a qualified object name that includes the name of the containing database or user. For example, database_name.object_name or user_name. object_name.
PROCEDURE
For procedures, you must specify a qualified object name that includes the name of the containing database or user. For example, database_name.object_name or user_name.object_name.
TABLE
For tables, you must specify a qualified object name that includes the name of the containing database or user. For example, database_name.object_name or user_name.object_name.
USER
For users, you must specify a qualified object name that includes the name of the containing database or user. For example, database_name.object_name or user_name.object_name.
VIEW
For views, you must specify a qualified object name that includes the name of the containing database or user. For example, database_name.object_name or user_name.object_name.
qualified_object_name
A qualified object name that includes the name of the containing database or user. For example, database_name.object_name or user_name.object_name.
TYPE
For user defined types, the specification must always be SYSUDTLIB.UDT_name, for example:
ON TYPE SYSUDTLIB. UDT_name