| title | Transactions | Microsoft Docs | |||
|---|---|---|---|---|
| ms.custom | ||||
| ms.date | 03/14/2017 | |||
| ms.prod | sql | |||
| ms.prod_service | database-engine, sql-database, sql-data-warehouse, pdw | |||
| ms.reviewer | ||||
| ms.technology | native-client | |||
| ms.topic | reference | |||
| helpviewer_keywords |
|
|||
| ms.assetid | 3b41e33a-c1ca-4b2a-9464-312b0ed3ca89 | |||
| author | markingmyname | |||
| ms.author | maghan | |||
| monikerRange | >=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current |
[!INCLUDEappliesto-ss-asdb-asdw-pdw-md]
The [!INCLUDEssNoVersion] Native Client OLE DB provider implements local transaction support. The consumer can use distributed or coordinated transactions by using Microsoft Distributed Transaction Coordinator (MS DTC). For consumers requiring transaction control that spans multiple sessions, the [!INCLUDEssNoVersion] Native Client OLE DB provider can join transactions initiated and maintained by MS DTC.
By default, the [!INCLUDEssNoVersion] Native Client OLE DB provider uses an autocommit transaction mode, where each discrete action on a consumer session comprises a complete transaction against an instance of [!INCLUDEssNoVersion]. The [!INCLUDEssNoVersion] Native Client OLE DB provider autocommit mode is local, and autocommit transactions never span more than a single session.
The [!INCLUDEssNoVersion] Native Client OLE DB provider exposes the ITransactionLocal interface, allowing the consumer to use explicitly and implicitly start transactions on a single connection to an instance of [!INCLUDEssNoVersion]. The [!INCLUDEssNoVersion] Native Client OLE DB provider does not support nested local transactions.