Skip to content

cursor-transaction-isolation-level.md

Latest commit

 

History

History
43 lines (32 loc) · 2.19 KB

cursor-transaction-isolation-level.md

File metadata and controls

43 lines (32 loc) · 2.19 KB
title Cursor Transaction Isolation Level | 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
isolation levels [ODBC]
ODBC applications, row versioning
cursors [ODBC], isolation levels
ODBC cursors, isolation levels
row versioning [SQL Server], ODBC
ms.assetid 0c6663a4-5a25-44aa-8fe4-e35af9bf4a83
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

Cursor Transaction Isolation Level

[!INCLUDEappliesto-ss-asdb-asdw-pdw-md]

The complete locking behavior of cursors is based on an interaction between concurrency attributes and the transaction isolation level set by the client. ODBC clients set the transaction isolation level using the SQLSetConnectAttr SQL_ATTR_TXN_ISOLATION or SQL_COPT_SS_TXN_ISOLATION attributes. The locking behavior of a specific cursor environment is determined by combining the locking behaviors of the concurrency and transaction isolation level options.

The following cursor transaction isolation levels are supported by the [!INCLUDEssNoVersion] Native Client ODBC driver:

  • Read committed (SQL_TXN_READ_COMMITTED)

  • Read uncommitted (SQL_TXN_READ_UNCOMMITTED)

  • Repeatable read (SQL_TXN_REPEATABLE_READ)

  • Serializable (SQL_TXN_SERIALIZABLE)

  • Snapshot (SQL_TXN_SS_SNAPSHOT)

Note that the ODBC API specifies additional transaction isolation levels, but these are not supported by [!INCLUDEssNoVersion] or the [!INCLUDEssNoVersion] Native Client ODBC driver.

See Also

Cursor Properties