Skip to content

Latest commit

 

History

History
40 lines (33 loc) · 1.83 KB

File metadata and controls

40 lines (33 loc) · 1.83 KB

title: "SQLColumnPrivileges | 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:

  • "SQLColumnPrivileges function" ms.assetid: c78acd4e-8668-4abc-9bc9-6ad381965863 caps.latest.revision: 33 author: "MightyPen" ms.author: "genemi" manager: "craigg" ms.workload: "Inactive" monikerRange: ">= aps-pdw-2016 || = azuresqldb-current || = azure-sqldw-latest || >= sql-server-2016 || = sqlallproducts-allversions"

SQLColumnPrivileges

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

SQLColumnPrivileges returns SQL_SUCCESS whether or not values exist for theCatalogName, SchemaName, TableName, or ColumnName parameters. SQLFetch returns SQL_NO_DATA when invalid values are used in these parameters.

SQLColumnPrivileges can be executed on a static server cursor. An attempt to execute SQLColumnPrivileges on an updatable (dynamic or keyset) cursor will return SQL_SUCCESS_WITH_INFO indicating that the cursor type has been changed.

The [!INCLUDEssNoVersion] Native Client ODBC driver supports reporting information for tables on linked servers by accepting a two-part name for the CatalogName parameter: Linked_Server_Name.Catalog_Name.

See Also

SQLColumnPrivileges Function
ODBC API Implementation Details