| title | Cursor Concurrency (ODBC) | Microsoft Docs | |||
|---|---|---|---|---|
| ms.custom | ||||
| ms.date | 03/06/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 | 68228ece-cbf1-4f19-bfdc-053884c1af48 | |||
| 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]
Cursor operations, like cursor types, are affected by the concurrency options set by the application. Concurrency options are set using the SQL_ATTR_CONCURRENCY option of SQLSetStmtAttr. The concurrency types are:
-
Read-only (SQL_CONCUR_READONLY)
-
Values (SQL_CONCUR_VALUES)
-
Row version (SQL_CONCUR_ROWVER)
-
Lock (SQL_CONCUR_LOCK)