15.00 - EXTERNAL SECURITY Clause - Teradata Database

Teradata Database SQL Data Definition Language Detailed Topics

Teradata Database
Release Number
Content Type
Programming Reference
Publication ID
English (United States)


This clause is mandatory for all external procedures that perform operating system I/O. Failing to specify this clause for a procedure that performs I/O can produce unpredictable results and even cause the database, if not the entire system, to reset.

Note that authorization_name is an optional Teradata extension to the ANSI SQL:2011 standard.

When a procedure definition specifies EXTERNAL SECURITY DEFINER, then that procedure executes in 1 of the following environments.

  • Specified OS platform user context of the associated security statement created for that purpose.
  • Same database or user in which the procedure is defined.
  • The following rules apply.

  • If you do not specify an authorization name, then you must create a default DEFINER authorization name (see “CREATE AUTHORIZATION/ REPLACE AUTHORIZATION” on page 206) before a user attempts to execute the procedure.
  • If you have specified an authorization name, then an object with that name must be created before the you can execute the procedure.
  • The system returns a warning message to the requestor when no authorization name exists at the time the procedure is being created.

    Related Topics


    For more information …

    See …

    on how to specify more than 1 encoded string per external routine definition

    the following topics.

  • “Include Name Clause” on page 279
  • “Library Name Clause” on page 280
  • “Object File Name Clause” on page 281
  • “Package Name Clause” on page 282
  • “Source File Name Clause” on page 283
  • on how to specify the C option in the external string literal clause

    “External String Literal” on page 276

    on default platform directories

    “UDF Default Location Paths” on page 287

    on how to specify external function names

    the following topics.

  • “Parameter Style Clause” on page 271
  • “Function Entry Name Clause” on page 278
  • “External String Literal” on page 276