SET SESSION DEBUG FUNCTION SQL Statement | Teradata Vantage - SET SESSION DEBUG FUNCTION - Advanced SQL Engine - Teradata Database

SQL Data Definition Language Syntax and Examples

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

Identifies the UDF, UDM, or stored procedure to be run in debug mode the next time the function, method, or stored procedure is invoked.

For more information, see CREATE PROCEDURE and REPLACE PROCEDURE (External Form), CREATE FUNCTION and REPLACE FUNCTION (External Form), CREATE METHOD, and “C/C++ Command-line Debugging for UDFs” in Teradata Vantage™ - SQL External Routine Programming , B035-1147 .

Required Privileges

You must have the EXECUTE FUNCTION and the DROP FUNCTION privilege on the function or stored procedure you want to debug.

You must have the UDTMETHOD and the UDTUSAGE privileges for the method you want to debug.

ANSI Compliance

SET SESSION DEBUG FUNCTION is a Teradata extension to the ANSI SQL:2011 standard.

Usage Notes

You can only debug one function per session at a time. After you set debugging on for a function, debugging remains enabled until one of the following occurs:
  • Debugging is turned off for the function.
  • Debugging is turned on for another function with a subsequent SET SESSION DEBUG FUNCTION statement.
  • The session terminates.

After you set debugging on for a function and a query invokes the function, the function is passed to the debugger. If a debugger is not active, the query cannot complete until the debugger is started, attaches to session running the query, and allows all instances of the function being debugged to complete.