| title | SQLGetCursorName | 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 | |
| apitype | DLLExport | |
| helpviewer_keywords |
|
|
| ms.assetid | 3a427a23-28ef-49aa-b9ec-6cab0914bdf3 | |
| 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]
If the application does not specify a cursor name, the [!INCLUDEssNoVersion] Native Client ODBC driver generates one for the application upon cursor generation. The application can use SQLGetCursorName to retrieve the driver-defined cursor name for positioned UPDATE and DELETE statements. The application does not need to call SQLSetCursorName to take advantage of positioned data manipulation statements.