executing-statements-odbc.md

title	description	author	ms.author	ms.date	ms.service	ms.subservice	ms.topic	helpviewer_keywords
Executing Statements (ODBC)	Executing Statements (ODBC)	markingmyname	maghan	03/14/2017	sql	native-client	reference	SQL Server Native Client ODBC driver, statements statements [ODBC] ODBC applications, statements statements [ODBC], executing

Executing Statements (ODBC)

[!INCLUDE SQL Server]

The [!INCLUDEssNoVersion] Native Client ODBC driver offers a variety ways to execute SQL statements in a [!INCLUDEssNoVersion] database:

• Direct execution

• Prepared execution

Direct execution involves building a character string containing a [!INCLUDEtsql] statement and submitting it for execution using the SQLExecDirect function. Prepared execution involves building a character string containing a [!INCLUDEtsql] statement and then executing it in two stages. The first stage uses the SQLPrepare Function function to parse and compile the execution plan for the statement in the [!INCLUDEssDE]. The second stage uses the SQLExecute function to execute the previously prepared execution plan. This saves the parsing and compiling overhead on each execution. Prepared execution is commonly used by applications to repeatedly execute the same, parameterized SQL statement.

Both direct and prepared execution can execute a single [!INCLUDEtsql] statement or a batch of SQL statements, or they can call a stored procedure.

In This Section

• Direct Execution

• Prepared Execution

• Procedures

• Batches of Statements

• Effects of ISO Options

See Also

Executing Queries (ODBC)