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.service: "" ms.component: "native-client-odbc-api" ms.reviewer: "" ms.suite: "sql" ms.technology:
ms.tgt_pltfrm: "" ms.topic: "reference" apitype: "DLLExport" helpviewer_keywords:
- "SQLGetCursorName function" ms.assetid: 3a427a23-28ef-49aa-b9ec-6cab0914bdf3 caps.latest.revision: 31 author: "MightyPen" ms.author: "genemi" manager: "craigg" ms.workload: "Inactive" monikerRange: ">= aps-pdw-2016 || = azuresqldb-current || = azure-sqldw-latest || >= sql-server-2016 || = sqlallproducts-allversions"
[!INCLUDEappliesto-ss-asdb-asdw-pdw-md] [!INCLUDESNAC_Deprecated]
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.