EXECUTE IMMEDIATE Statement [ESQL] [SP]

Enables dynamically constructed statements to be executed from within a procedure.

Syntax

Syntax 1

EXECUTE IMMEDIATE [ execute-option ] string-expression

execute-option:
WITH QUOTES [ ON | OFF ]
| WITH ESCAPES { ON | OFF } 
| WITH RESULT SET { ON | OFF }

Syntax 2

EXECUTE ( string-expression )

Examples

Example 1 – This procedure creates a table, where the table name is supplied as a parameter to the procedure. The full EXECUTE IMMEDIATE statement must be on a single line.
```
CREATE PROCEDURE CreateTableProc(
            IN tablename char(30)
            )
BEGIN
 EXECUTE IMMEDIATE 'CREATE TABLE ' || tablename ||
' ( column1 INT PRIMARY KEY)'
END;
```
Call the procedure and create table mytable:
```
CALL CreateTableProc( 'mytable' )
```

Usage

EXECUTE IMMEDIATE extends the range of statements that can be executed from within procedures. It lets you execute dynamically prepared statements, such as statements that are constructed using the parameters passed in to a procedure.

Literal strings in the statement must be enclosed in single quotes, and must differ from any existing statement name in a PREPARE or EXECUTE IMMEDIATE statement. The statement must be on a single line.

Only global variables can be referenced in a statement executed by EXECUTE IMMEDIATE.

Only syntax 2 can be used inside Transact-SQL stored procedures.

WITH QUOTES—When you specify WITH QUOTES or WITH QUOTES ON, any double quotes in the string expression are assumed to delimit an identifier. When you do not specify WITH QUOTES, or specify WITH QUOTES OFF, the treatment of double quotes in the string expression depends on the current setting of the QUOTED_IDENTIFIER option.

WITH QUOTES is useful when an object name that is passed into the stored procedure is used to construct the statement that is to be executed, but the name might require double quotes and the procedure might be called when QUOTED_IDENTIFIER is set to OFF.

See QUOTED_IDENTIFIER Option [TSQL].

WITH ESCAPES—WITH ESCAPES OFF causes any escape sequences (such as \n, \x, or \\) in the string expression to be ignored. For example, two consecutive backslashes remain as two backslashes, rather than being converted to a single backslash. The default setting is equivalent to WITH ESCAPES ON.

You can use WITH ESCAPES OFF for easier execution of dynamically constructed statements referencing file names that contain backslashes.

In some contexts, escape sequences in the string-expression are transformed before EXECUTE IMMEDIATE is executed. For example, compound statements are parsed before being executed, and escape sequences are transformed during this parsing, regardless of the WITH ESCAPES setting. In these contexts, WITH ESCAPES OFF prevents further translations from occurring. For example:

BEGIN
DECLARE String1 LONG VARCHAR;
DECLARE String2 LONG VARCHAR;
EXECUTE IMMEDIATE 
 'SET String1 = ''One backslash: \\\\ '''; 
 EXECUTE IMMEDIATE WITH ESCAPES OFF 
 'SET String2 = ''Two backslashes: \\\\ ''';  
 SELECT String1, String2 
END

WITH RESULT SET—You can have an EXECUTE IMMEDIATE statement return a result set by specifying WITH RESULT SET ON. With this clause, the containing procedure is marked as returning a result set. If you do not include this clause, an error is reported when the procedure is called if the statement does not produce a result set.

Note: The default option is WITH RESULT SET OFF, meaning that no result set is produced when the statement is executed.

Side Effects

None. However, if the statement is a data definition statement with an automatic commit as a side effect, then that commit does take place.

Standards

SQL—ISO/ANSI SQL compliant.
Sybase—Supported in Open Client/Open Server.

Permissions

None. The statement is executed with the permissions of the owner of the procedure, not with the permissions of the user who calls the procedure.