DENY Server Principal Permissions (Transact-SQL)

**APPLIES TO:** ![yes](media/yes.png)SQL Server (starting with 2008) ![no](media/no.png)Azure SQL Database ![no](media/no.png)Azure SQL Data Warehouse ![no](media/no.png)Parallel Data Warehouse

Denies permissions granted on a SQL Server 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 SQL Server login. For a list of the permissions, see the Remarks section later in this topic.

LOGIN :: SQL_Server_login
Specifies the SQL Server 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 SQL Server login or server role to which the permission is being granted.

TO SQL_Server_login
Specifies the SQL Server login to which the permission is being denied.

SQL_Server_login
Specifies the name of a SQL Server login.

SQL_Server_login_from_Windows_login
Specifies the name of a SQL Server login created from a Windows login.

SQL_Server_login_from_certificate
Specifies the name of a SQL Server login mapped to a certificate.

SQL_Server_login_from_AsymKey
Specifies the name of a SQL Server 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 SQL Server 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.

SQL Server logins and server roles are server-level securables. The most specific and limited permissions that can be denied on a SQL Server SQL Server 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

The following example denies IMPERSONATE permission on the SQL Server login WanidaBenshoof to a SQL Server SQL Server 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 SQL Server login EricKurjan to SQL Server SQL Server 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