A name to be used for this authorization so it can be invoked within an external routine definition. See CREATE FUNCTION and REPLACE FUNCTION (External Form), CREATE FUNCTION and REPLACE FUNCTION (Table Form), CREATE METHOD, and CREATE PROCEDURE and REPLACE PROCEDURE (External Form).
For information about naming database objects, see Teradata Vantage™ SQL Fundamentals, B035-1141.
- Authorizations belong to the database or user in which they are created and are not valid in other databases or users. For information about using authorization objects with the Script Table Operator, see Teradata Vantage™ SQL Operators and User-Defined Functions, B035-1210.
- An authorization object name cannot begin with a digit.
- An authorization object name cannot be an SQL keyword.
- An authorization object name must be unique within its containing database or user.
- The name of an authorization object must conform to object naming rules.
- Optional name of a database or user other than the current or default in which the authorization being defined or replaced is to be contained.
- The following rules apply to specifying DEFINER or INVOKER.
- A database or user can be associated with only one INVOKER authorization object name.
- A database or user can be associated with only one default DEFINER authorization object name.
- A database or user can be associated with many non-default DEFINER authorization object names.
- If you specify DEFINER, the database or user you specify must be the containing database or user for the UDF, table UDF, method, or external SQL procedure.
- If you specify INVOKER, the database or user you specify must be the logon database or user for a user or profile.