Grants one or more explicit privileges on a database, user, proxy logon user, table, hash index, join index, view, procedure, User-Defined Function (UDF), function mapping, User-Defined Method (UDM), User-Defined Type (UDT), or macro to a role, group of roles, user, or group of users or databases.
For a list of database privileges, see Database Privileges.
For information about granting the NONTEMPORAL privilege, see Teradata Vantage™ - Temporal Table Support, B035-1182.
ANSI Compliance
This statement is a Teradata extension to the ANSI SQL:2011 standard.
Required Privileges
- User DBC.
- An owner of the object.
For details regarding security issues associated with owner privileges, see Security Considerations with the CREATE MACRO Privilege
- A user possessing each privilege to be granted.
A privilege can be granted to a user explicitly or the user can inherit the privilege from a role as a result of creating a view, macro, or procedure.
- OVERRIDE DELETE CONSTRAINT
- OVERRIDE DUMP CONSTRAINT
- OVERRIDE INSERT CONSTRAINT
- OVERRIDE RESTORE CONSTRAINT
- OVERRIDE SELECT CONSTRAINT
- OVERRIDE UPDATE CONSTRAINT
- A user need not be related to a grantor through ownership to receive a privilege.
A grantor does not need to have any privilege, including WITH ADMIN OPTION, on the grantee to grant a privilege to it, whether the grantee is a role, a user, database, or PUBLIC.
- If a GRANT statement is on a database or user, the privilege applies to all objects, both current and future, created in that space.
If a REVOKE statement removes the privilege, the privilege is dropped for all objects.
A REVOKE statement at the object level cannot remove a privilege from that object that was granted on the database or user.
- When you specify the WITH GRANT OPTION phrase, the recipient of the privilege can then grant that privilege to other users.
You implicitly have the WITH GRANT OPTION privilege on any database, user, or object you own.
Owner Can Explicitly Grant Any or All Privileges on Any of the Following Privilege Can Be Granted to the Following - Child database
- Child user
- Database object
- Another database
- Another user
- Role
- PUBLIC
You cannot assign row-level security privileges to PUBLIC.
- Any privilege granted automatically or explicitly can be revoked using the REVOKE statement.
See REVOKE (SQL Form).
- Implicit privileges cannot be revoked.
When Privileges Are Granted
GRANT takes effect immediately when the grantee issues their next statement. You do not need to log out to receive a privilege that was just granted to you.