GRANT Service Broker Permissions (Transact-SQL)

GRANT Service Broker Permissions (Transact-SQL)

 

Updated: June 10, 2016

THIS TOPIC APPLIES TO:yesSQL Server (starting with 2008)noAzure SQL DatabasenoAzure SQL Data Warehouse noParallel Data Warehouse

Grants permissions on a Service Broker contract, message type, remote binding, route, or service.

Topic link icon Transact-SQL Syntax Conventions

  
GRANT permission  [ ,...n ] ON  
    {    
              [ CONTRACT :: contract_name ]   
       | [ MESSAGE TYPE :: message_type_name ]    
       | [ REMOTE SERVICE BINDING :: remote_binding_name ]    
       | [ ROUTE :: route_name ]   
       | [ SERVICE :: service_name ]      
    }  
    TO database_principal [ ,...n ]   
    [ WITH GRANT OPTION ]  
        [ AS granting_principal ]  

permission
Specifies a permission that can be granted on a Service Broker securable. Listed below.

CONTRACT ::contract_name
Specifies the contract on which the permission is being granted. The scope qualifier "::" is required.

MESSAGE TYPE ::message_type_name
Specifies the message type on which the permission is being granted. The scope qualifier "::" is required.

REMOTE SERVICE BINDING ::remote_binding_name
Specifies the remote service binding on which the permission is being granted. The scope qualifier "::" is required.

ROUTE ::route_name
Specifies the route on which the permission is being granted. The scope qualifier "::" is required.

SERVICE ::service_name
Specifies the service on which the permission is being granted. The scope qualifier "::" is required.

database_principal
Specifies the principal to which the permission is being granted. One of the following:

  • database user

  • database role

  • application role

  • database user mapped to a Windows login

  • database user mapped to a Windows group

  • database user mapped to a certificate

  • database user mapped to an asymmetric key

  • database user not mapped to a server principal.

GRANT OPTION
Indicates that the principal will also be given the ability to grant the specified permission to other principals.

granting_principal
Specifies a principal from which the principal executing this query derives its right to grant the permission. One of the following:

  • database user

  • database role

  • application role

  • database user mapped to a Windows login

  • database user mapped to a Windows group

  • database user mapped to a certificate

  • database user mapped to an asymmetric key

  • database user not mapped to a server principal.

A Service Broker contract is a database-level securable contained by the database that is its parent in the permissions hierarchy. The most specific and limited permissions that can be granted on a Service Broker contract are listed below, together with the more general permissions that include them by implication.

Service Broker contract permissionImplied by Service Broker contract permissionImplied by database permission
CONTROLCONTROLCONTROL
TAKE OWNERSHIPCONTROLCONTROL
ALTERCONTROLALTER ANY CONTRACT
REFERENCESCONTROLREFERENCES
VIEW DEFINITIONCONTROLVIEW DEFINITION

A Service Broker message type is a database-level securable contained by the database that is its parent in the permissions hierarchy. The most specific and limited permissions that can be granted on a Service Broker message type are listed below, together with the more general permissions that include them by implication.

Service Broker message type permissionImplied by Service Broker message type permissionImplied by database permission
CONTROLCONTROLCONTROL
TAKE OWNERSHIPCONTROLCONTROL
ALTERCONTROLALTER ANY MESSAGE TYPE
REFERENCESCONTROLREFERENCES
VIEW DEFINITIONCONTROLVIEW DEFINITION

A Service Broker remote service binding is a database-level securable contained by the database that is its parent in the permissions hierarchy. The most specific and limited permissions that can be granted on a Service Broker remote service binding are listed below, together with the more general permissions that include them by implication.

Service Broker remote service binding permissionImplied by Service Broker remote service binding permissionImplied by database permission
CONTROLCONTROLCONTROL
TAKE OWNERSHIPCONTROLCONTROL
ALTERCONTROLALTER ANY REMOTE SERVICE BINDING
VIEW DEFINITIONCONTROLVIEW DEFINITION

A Service Broker route is a database-level securable contained by the database that is its parent in the permissions hierarchy. The most specific and limited permissions that can be granted on a Service Broker route are listed below, together with the more general permissions that include them by implication.

Service Broker route permissionImplied by Service Broker route permissionImplied by database permission
CONTROLCONTROLCONTROL
TAKE OWNERSHIPCONTROLCONTROL
ALTERCONTROLALTER ANY ROUTE
VIEW DEFINITIONCONTROLVIEW DEFINITION

Service Broker Services

A Service Broker service is a database-level securable contained by the database that is its parent in the permissions hierarchy. The most specific and limited permissions that can be granted on a Service Broker service are listed below, together with the more general permissions that include them by implication.

Service Broker service permissionImplied by Service Broker service permissionImplied by database permission
CONTROLCONTROLCONTROL
TAKE OWNERSHIPCONTROLCONTROL
SENDCONTROLCONTROL
ALTERCONTROLALTER ANY SERVICE
VIEW DEFINITIONCONTROLVIEW DEFINITION

The grantor (or the principal specified with the AS option) must have either the permission itself with GRANT OPTION, or a higher permission that implies the permission being granted.

If using the AS option, these additional requirements apply.

AS granting_principalAdditional permission required
Database userIMPERSONATE permission on the user, membership in the db_securityadmin fixed database role, membership in the db_owner fixed database role, or membership in the sysadmin fixed server role.
Database user mapped to a Windows loginIMPERSONATE permission on the user, membership in the db_securityadmin fixed database role, membership in the db_owner fixed database role, or membership in the sysadmin fixed server role.
Database user mapped to a Windows groupMembership in the Windows group, membership in the db_securityadmin fixed database role, membership in the db_owner fixed database role, or membership in the sysadmin fixed server role.
Database user mapped to a certificateMembership in the db_securityadmin fixed database role, membership in the db_owner fixed database role, or membership in the sysadmin fixed server role.
Database user mapped to an asymmetric keyMembership in the db_securityadmin fixed database role, membership in the db_owner fixed database role, or membership in the sysadmin fixed server role.
Database user not mapped to any server principalIMPERSONATE permission on the user, membership in the db_securityadmin fixed database role, membership in the db_owner fixed database role, or membership in the sysadmin fixed server role.
Database roleALTER permission on the role, membership in the db_securityadmin fixed database role, membership in the db_owner fixed database role, or membership in the sysadmin fixed server role.
Application roleALTER permission on the role, membership in the db_securityadmin fixed database role, membership in the db_owner fixed database role, or membership in the sysadmin fixed server role.

Object owners can grant permissions on the objects they own. Principals with CONTROL permission on a securable can grant permission on that securable.

Grantees of CONTROL SERVER permission, such as members of the sysadmin fixed server role, can grant any permission on any securable in the server. Grantees of CONTROL permission on a database, such as members of the db_owner fixed database role, can grant any permission on any securable in the database. Grantees of CONTROL permission on a schema can grant any permission on any object within the schema.

SQL Server Service Broker
GRANT (Transact-SQL)
Permissions (Database Engine)
Principals (Database Engine)

Community Additions

ADD
Show:
© 2016 Microsoft