Granting SQL DML OVERRIDE Privileges - Advanced SQL Engine

Granting SQL DML OVERRIDE Privileges - Advanced SQL Engine - Teradata Database

Security Administration

Product

Advanced SQL Engine

Teradata Database

Release Number

17.05

17.00

Published

September 2020

Language

English (United States)

Last Update

2021-01-23

dita:mapPath

ied1556235912841.ditamap

dita:ditavalPath

lze1555437562152.ditaval

dita:id

B035-1100

lifecycle

Product Category

Teradata Vantage™

You can grant OVERRIDE privileges using the GRANT (SQL form) statement. For example:

GRANT OVERRIDE [sql_statement_type  ... [,  sql_statement_type]] CONSTRAINT [constraint_name  ... [, constraint_name]]
ON [object_name]
TO  user_name  ...[, user_name]|role_name...[,role_name]

where:

Syntax Element	Description
[sql_statement_type... [,sql_statement_type]]	The SQL statement type(s) for which OVERRIDE privileges are granted, INSERT, SELECT, UPDATE, or DELETE. If no SQL statement is specified, the OVERRIDE privilege is granted for all SQL statement types.
CONSTRAINT [constraint_name... [,constraint_name]]	The row level security constraints that are subject to the OVERRIDE privilege(s). If no security constraint name is specified, the keyword CONSTRAINT is still required, and OVERRIDE privileges apply to all security constraints for the object specification.
[object_name]	The object on which the OVERRIDE is granted. If no object is specified, the privileges apply to all database objects except database DBC objects.
user_name ...[, user_name] \| role_name...[,role_name]	The user(s) or role(s) to which the OVERRIDE privileges are granted. OVERRIDE privileges cannot be granted to PUBLIC. The named role can be a database role or an external role.