| title | titleSuffix | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | dev_langs | monikerRange | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
GRANT Database Principal Permissions |
SQL Server (Transact-SQL) |
Grant permissions on a database user, database role, or application role. |
VanMSFT |
vanto |
03/12/2017 |
sql |
t-sql |
reference |
|
|
>=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current||=fabric |
[!INCLUDE sql-asdb-asdbmi-asa-pdw-fabricse-fabricdw]
Grants permissions on a database user, database role, or application role in [!INCLUDEssNoVersion].
:::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: Transact-SQL syntax conventions
GRANT permission [ ,...n ]
ON
{ [ USER :: database_user ]
| [ ROLE :: database_role ]
| [ APPLICATION ROLE :: application_role ]
}
TO <database_principal> [ ,...n ]
[ WITH GRANT OPTION ]
[ AS <database_principal> ]
<database_principal> ::=
Database_user
| Database_role
| Application_role
| Database_user_mapped_to_Windows_User
| Database_user_mapped_to_Windows_Group
| Database_user_mapped_to_certificate
| Database_user_mapped_to_asymmetric_key
| Database_user_with_no_login
permission
Specifies a permission that can be granted on the database principal. For a list of the permissions, see the Remarks section later in this topic.
USER ::database_user
Specifies the class and name of the user on which the permission is being granted. The scope qualifier (::) is required.
ROLE ::database_role
Specifies the class and name of the role on which the permission is being granted. The scope qualifier (::) is required.
APPLICATION ROLE ::application_role
Specifies the class and name of the application role on which the permission is being granted. The scope qualifier (::) is required.
WITH GRANT OPTION
Indicates that the principal will also be given the ability to grant the specified permission to other principals.
AS <database_principal>
Specifies a principal from which the principal executing this query derives its right to grant the permission.
Database_user
Specifies a database user.
Database_role
Specifies a database role.
Application_role
Applies to: [!INCLUDEsql2008-md] and later, [!INCLUDEsssds].
Specifies an application role.
Database_user_mapped_to_Windows_User
Specifies a database user mapped to a Windows user.
Database_user_mapped_to_Windows_Group
Specifies a database user mapped to a Windows group.
Database_user_mapped_to_certificate
Specifies a database user mapped to a certificate.
Database_user_mapped_to_asymmetric_key
Specifies a database user mapped to an asymmetric key.
Database_user_with_no_login
Specifies a database user with no corresponding server-level principal.
Information about database principals is visible in the sys.database_principals catalog view. Information about database-level permissions is visible in the sys.database_permissions catalog view.
A database user 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 database user are listed in the following table, together with the more general permissions that include them by implication.
| Database user permission | Implied by database user permission | Implied by database permission |
|---|---|---|
| CONTROL | CONTROL | CONTROL |
| IMPERSONATE | CONTROL | CONTROL |
| ALTER | CONTROL | ALTER ANY USER |
| VIEW DEFINITION | CONTROL | VIEW DEFINITION |
A database role 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 database role are listed in the following table, together with the more general permissions that include them by implication.
| Database role permission | Implied by database role permission | Implied by database permission |
|---|---|---|
| CONTROL | CONTROL | CONTROL |
| TAKE OWNERSHIP | CONTROL | CONTROL |
| ALTER | CONTROL | ALTER ANY ROLE |
| VIEW DEFINITION | CONTROL | VIEW DEFINITION |
An application role 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 an application role are listed in the following, together with the more general permissions that include them by implication.
| Application role permission | Implied by application role permission | Implied by database permission |
|---|---|---|
| CONTROL | CONTROL | CONTROL |
| ALTER | CONTROL | ALTER ANY APPLICATION ROLE |
| VIEW DEFINITION | CONTROL | VIEW 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 you are using the AS option, the following additional requirements apply.
| AS granting_principal | Additional permission required |
|---|---|
| Database user | IMPERSONATE 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 User | IMPERSONATE 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 Group | Membership 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 certificate | 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 an asymmetric key | Membership in the db_securityadminfixed 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 principal | IMPERSONATE 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 role | ALTER permission on the role, membership in the db_securityadminfixed database role, membership in the db_owner fixed database role, or membership in the sysadmin fixed server role. |
| Application role | ALTER 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. |
Principals that have CONTROL permission on a securable can grant permission on that securable.
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.
The following example grants CONTROL permission on [!INCLUDE sssampledbobject-md] user Wanida to user RolandX.
GRANT CONTROL ON USER::Wanida TO RolandX;
GO The following example grants VIEW DEFINITION permission on [!INCLUDE sssampledbobject-md] role SammamishParking together with GRANT OPTION to database user JinghaoLiu.
GRANT VIEW DEFINITION ON ROLE::SammamishParking
TO JinghaoLiu WITH GRANT OPTION;
GO The following example grants IMPERSONATE permission on user HamithaL to [!INCLUDE sssampledbobject-md] application role AccountsPayable17.
Applies to: [!INCLUDEsql2008-md] and later, [!INCLUDEsssds].
GRANT IMPERSONATE ON USER::HamithaL TO AccountsPayable17;
GO DENY Database Principal Permissions (Transact-SQL)
REVOKE Database Principal Permissions (Transact-SQL)
sys.database_principals (Transact-SQL)
sys.database_permissions (Transact-SQL)
CREATE USER (Transact-SQL)
CREATE APPLICATION ROLE (Transact-SQL)
CREATE ROLE (Transact-SQL)
GRANT (Transact-SQL)
Permissions (Database Engine)
Principals (Database Engine)