DENY Endpoint Permissions (Transact-SQL)

Applies to: SQL Server Azure SQL Managed Instance

Denies permissions on an endpoint.

Transact-SQL syntax conventions

Syntax

DENY permission  [ ,...n ] ON ENDPOINT :: endpoint_name  
    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  

Note

To view Transact-SQL syntax for SQL Server 2014 (12.x) and earlier versions, see Previous versions documentation.

Arguments

permission
Specifies a permission that can be denied on an endpoint. For a list of the permissions, see the Remarks section later in this topic.

ON ENDPOINT ::endpoint_name
Specifies the endpoint on which the permission is being denied. The scope qualifier (::) is required.

TO <server_principal>
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.

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 endpoints is visible in the sys.endpoints catalog view. Information about server permissions is visible in the sys.server_permissions catalog view, and information about server principals is visible in the sys.server_principals catalog view.

An endpoint is a server-level securable. The most specific and limited permissions that can be denied on an endpoint are listed in the following table, together with the more general permissions that include them by implication.

Endpoint permission Implied by endpoint permission Implied by server permission
ALTER CONTROL ALTER ANY ENDPOINT
CONNECT CONTROL CONTROL SERVER
CONTROL CONTROL CONTROL SERVER
TAKE OWNERSHIP CONTROL CONTROL SERVER
VIEW DEFINITION CONTROL VIEW ANY DEFINITION

Permissions

Requires CONTROL permission on the endpoint or ALTER ANY ENDPOINT permission on the server.

Examples

A. Denying VIEW DEFINITION permission on an endpoint

The following example denies VIEW DEFINITION permission on the endpoint Mirror7 to the SQL Server login ZArifin.

USE master;  
DENY VIEW DEFINITION ON ENDPOINT::Mirror7 TO ZArifin;  
GO  

B. Denying TAKE OWNERSHIP permission with CASCADE option

The following example denies TAKE OWNERSHIP permission on the endpoint Shipping83 to the SQL Server user PKomosinski and to principals to which PKomosinski granted TAKE OWNERSHIP.

USE master;  
DENY TAKE OWNERSHIP ON ENDPOINT::Shipping83 TO PKomosinski   
    CASCADE;  
GO  

See Also

GRANT Endpoint Permissions (Transact-SQL)
REVOKE Endpoint Permissions (Transact-SQL)
CREATE ENDPOINT (Transact-SQL)
Endpoints Catalog Views (Transact-SQL)
sys.endpoints (Transact-SQL)
Permissions (Database Engine)
Principals (Database Engine)