DCL Statements in Stored Procedures | Teradata Vantage - DCL Statements in Stored Procedures - Advanced SQL Engine - Teradata Database

SQL Stored Procedures and Embedded SQL

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
xqq1557098602407.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1148
lifecycle
previous
Product Category
Teradata Vantage™

Supported DCL Statements

You can use the following SQL DCL statements in a stored procedure.

  • GIVE
  • GRANT (all forms)
  • GRANT CONNECT THROUGH
  • GRANT LOGON
  • REVOKE (all forms)
  • REVOKE CONNECT THROUGH
  • REVOKE LOGON

Transaction Mode Impact on DCL Statements

The behavior of DCL statements specified in stored procedures at runtime depends on the transaction mode of the Teradata session in which the procedure is created.

  • A DCL statement specified within an explicit (user-defined) transaction in a stored procedure in Teradata transaction mode must be the last statement in that transaction. Otherwise, a runtime exception (SQLCODE: 3932, SQLSTATE: ‘T3932’) is raised.
  • When performing a stored procedure in ANSI transaction mode, each DCL statement specified in the procedure body must be followed by a COMMIT WORK statement. Otherwise, a runtime exception (SQLCODE: 3722, SQLSTATE: ‘T3722’) is raised.