Skip to content

Latest commit

 

History

History
151 lines (116 loc) · 7.62 KB

deny-server-principal-permissions-transact-sql.md

File metadata and controls

151 lines (116 loc) · 7.62 KB
title ms.custom ms.date ms.prod ms.prod_service ms.reviewer ms.technology ms.topic dev_langs helpviewer_keywords ms.assetid author ms.author
DENY Server Principal Permissions (Transact-SQL) | Microsoft Docs
06/09/2017
sql
sql-database
t-sql
language-reference
TSQL
DENY statement, impersonate
permissions [SQL Server], impersonate
impersonate [SQL Server], denying
DENY statement, logins
permissions [SQL Server], logins
denying permissions [SQL Server], logins
servers [SQL Server], permissions
logins [SQL Server], denying access
859affa7-0567-47d1-9490-57c1abbd619b
VanMSFT
vanto

DENY Server Principal Permissions (Transact-SQL)

[!INCLUDEtsql-appliesto-ss2008-xxxx-xxxx-xxx-md]

Denies permissions granted on a [!INCLUDEssNoVersion] login.

Topic link icon Transact-SQL Syntax Conventions

Syntax

DENY permission [ ,...n ] }   
    ON   
    { [ LOGIN :: SQL_Server_login ]  
      | [ SERVER ROLE :: server_role ] }   
    TO <server_principal> [ ,...n ]  
    [ CASCADE ]  
    [ AS SQL_Server_login ]   
  
<server_principal> ::=   
    SQL_Server_login  
    | SQL_Server_login_from_Windows_login   
    | SQL_Server_login_from_certificate   
    | SQL_Server_login_from_AsymKey   
    | server_role  

Arguments

permission
Specifies a permission that can be denies on a [!INCLUDEssNoVersion] login. For a list of the permissions, see the Remarks section later in this topic.

LOGIN :: SQL_Server_login
Specifies the [!INCLUDEssNoVersion] login on which the permission is being denied. The scope qualifier (::) is required.

SERVER ROLE :: server_role
Specifies the server role on which the permission is being denied. The scope qualifier (::) is required.

TO <server_principal>
Specifies the [!INCLUDEssNoVersion] login or server role to which the permission is being granted.

TO SQL_Server_login
Specifies the [!INCLUDEssNoVersion] login to which the permission is being denied.

SQL_Server_login
Specifies the name of a [!INCLUDEssNoVersion] login.

SQL_Server_login_from_Windows_login
Specifies the name of a [!INCLUDEssNoVersion] login created from a Windows login.

SQL_Server_login_from_certificate
Specifies the name of a [!INCLUDEssNoVersion] login mapped to a certificate.

SQL_Server_login_from_AsymKey
Specifies the name of a [!INCLUDEssNoVersion] login mapped to an asymmetric key.

server_role
Specifies the name of a server role.

CASCADE
Indicates that the permission being denied is also denied to other principals to which it has been granted by this principal.

AS SQL_Server_login
Specifies the [!INCLUDEssNoVersion] login from which the principal executing this query derives its right to deny the permission.

Remarks

Permissions at the server scope can be denied only when the current database is master.

Information about server permissions is available in the sys.server_permissions catalog view. Information about server principals is available in the sys.server_principals catalog view.

The DENY statement fails if CASCADE is not specified when you are denying a permission to a principal that was granted that permission with GRANT OPTION.

[!INCLUDEssNoVersion] logins and server roles are server-level securables. The most specific and limited permissions that can be denied on a [!INCLUDEssNoVersion] login or server role are listed in the following table, together with the more general permissions that include them by implication.

SQL Server login or server role permission Implied by SQL Server login or server role permission Implied by server permission
CONTROL CONTROL CONTROL SERVER
IMPERSONATE CONTROL CONTROL SERVER
VIEW DEFINITION CONTROL VIEW ANY DEFINITION
ALTER CONTROL ALTER ANY LOGIN

ALTER ANY SERVER ROLE

Permissions

For logins, requires CONTROL permission on the login or ALTER ANY LOGIN permission on the server.

For server roles, requires CONTROL permission on the server role or ALTER ANY SERVER ROLE permission on the server.

Examples

A. Denying IMPERSONATE permission on a login

The following example denies IMPERSONATE permission on the [!INCLUDEssNoVersion] login WanidaBenshoof to a [!INCLUDEssNoVersion] login created from the Windows user AdvWorks\YoonM.

USE master;  
DENY IMPERSONATE ON LOGIN::WanidaBenshoof TO [AdvWorks\YoonM];  
GO  

B. Denying VIEW DEFINITION permission with CASCADE

The following example denies VIEW DEFINITION permission on the [!INCLUDEssNoVersion] login EricKurjan to [!INCLUDEssNoVersion] login RMeyyappan. The CASCADE option indicates that VIEW DEFINITION permission on EricKurjan will also be denied to principals to which RMeyyappan granted this permission.

USE master;  
DENY VIEW DEFINITION ON LOGIN::EricKurjan TO RMeyyappan   
    CASCADE;  
GO   

C. Denying VIEW DEFINITION permission on a server role

The following example denies VIEW DEFINITION on the Sales server role to the Auditors server role.

USE master;  
DENY VIEW DEFINITION ON SERVER ROLE::Sales TO Auditors ;  
GO   

See Also

sys.server_principals (Transact-SQL)
sys.server_permissions (Transact-SQL)
GRANT Server Principal Permissions (Transact-SQL)
REVOKE Server Principal Permissions (Transact-SQL)
CREATE LOGIN (Transact-SQL)
Principals (Database Engine)
Permissions (Database Engine)
Security Functions (Transact-SQL)
Security Stored Procedures (Transact-SQL)