| title | Freeing a Statement Handle | Microsoft Docs | ||||||
|---|---|---|---|---|---|---|---|
| ms.custom | |||||||
| ms.date | 03/06/2017 | ||||||
| ms.prod | sql-server-2014 | ||||||
| ms.reviewer | |||||||
| ms.technology | native-client | ||||||
| ms.topic | reference | ||||||
| helpviewer_keywords |
|
||||||
| ms.assetid | 96fdff84-0ca7-460a-a240-94ee826ea41c | ||||||
| author | MightyPen | ||||||
| ms.author | genemi | ||||||
| manager | craigg |
It is more efficient to reuse statement handles than to drop them and allocate new ones. Before executing a new SQL statement on a statement handle, applications should verify that the current statement settings are appropriate. These include statement attributes, parameter bindings, and result set bindings. Generally, parameters and result sets for the old SQL statement must be unbound by calling SQLFreeStmt with the SQL_RESET_PARAMS and SQL_UNBIND options and then re-bound for the new SQL statement.
When the application has finished using the statement, it calls SQLFreeHandle to free the statement. Note that SQLDisconnect automatically frees all statements on a connection.