| description | Manual-Commit Mode | ||||||
|---|---|---|---|---|---|---|---|
| title | Manual-Commit Mode | Microsoft Docs | ||||||
| ms.custom | |||||||
| ms.date | 01/19/2017 | ||||||
| ms.prod | sql | ||||||
| ms.prod_service | connectivity | ||||||
| ms.reviewer | |||||||
| ms.technology | connectivity | ||||||
| ms.topic | conceptual | ||||||
| helpviewer_keywords |
|
||||||
| ms.assetid | 9c4b3931-e48b-4960-89a2-5697537e9f51 | ||||||
| author | David-Engel | ||||||
| ms.author | v-daenge |
In manual-commit mode, applications must explicitly complete transactions by calling SQLEndTran to commit them or roll them back. This is the normal transaction mode for most relational databases.
Transactions in ODBC do not have to be explicitly initiated. Instead, a transaction begins implicitly whenever the application starts operating on the database. If the data source requires explicit transaction initiation, the driver must provide it whenever the application executes a statement requiring a transaction and there is no current transaction.