Skip to content

Latest commit

 

History

History
82 lines (61 loc) · 4.08 KB

deny-system-object-permissions-transact-sql.md

File metadata and controls

82 lines (61 loc) · 4.08 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic helpviewer_keywords dev_langs
DENY System Object Permissions (Transact-SQL)
DENY System Object Permissions (Transact-SQL)
VanMSFT
vanto
06/10/2016
sql
t-sql
reference
DENY statement, system objects
encryption [SQL Server], system objects
system objects [SQL Server]
cryptography [SQL Server], system objects
TSQL

DENY System Object Permissions (Transact-SQL)

[!INCLUDE SQL Server Azure SQL Database Azure SQL Managed Instance]

Denies permissions on system objects such as stored procedures, extended stored procedures, functions, and views.

:::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: Transact-SQL syntax conventions

Syntax

DENY { SELECT | EXECUTE } ON [ sys.]system_object TO principal

Arguments

[ sys.]
The sys qualifier is required only when you are referring to catalog views and dynamic management views.

system_object
Specifies the object on which permission is being denied.

principal
Specifies the principal from which the permission is being revoked.

Remarks

This statement can be used to deny permissions on certain stored procedures, extended stored procedures, table-valued functions, scalar functions, views, catalog views, compatibility views, INFORMATION_SCHEMA views, dynamic management views, and system tables that are installed by [!INCLUDEssNoVersion]. Each of these system objects exists as a unique record in the resource database (mssqlsystemresource). The resource database is read-only. A link to the object is exposed as a record in the sys schema of every database.

Default name resolution resolves unqualified procedure names to the resource database. Therefore, the sys qualifier is only required when you are specifying catalog views and dynamic management views.

Caution

Denying permissions on system objects will cause applications that depend on them to fail. [!INCLUDEssManStudioFull] uses catalog views and may not function as expected if you change the default permissions on catalog views.

Denying permissions on triggers and on columns of system objects is not supported.

Permissions on system objects will be preserved during upgrades of [!INCLUDEssNoVersion].

System objects are visible in the sys.system_objects catalog view. The permissions on system objects are visible in the sys.database_permissions catalog view in the master database.

The following query returns information about permissions of system objects:

SELECT * FROM master.sys.database_permissions AS dp   
    JOIN sys.system_objects AS so  
    ON dp.major_id = so.object_id  
    WHERE dp.class = 1 AND so.parent_object_id = 0 ;  
GO

Permissions

Requires CONTROL SERVER permission.

Examples

The following example denies EXECUTE permission on xp_cmdshell to public.

DENY EXECUTE ON sys.xp_cmdshell TO public;  
GO

See Also

Transact-SQL syntax conventions
sys.database_permissions (Transact-SQL)
GRANT System Object Permissions (Transact-SQL)
REVOKE System Object Permissions (Transact-SQL)