sp_addrolemember (Transact-SQL)

Syntax

sp_addrolemember [ @rolename = ] 'role',
    [ @membername = ] 'security_account'

Arguments

• [ @rolename= ] 'role'
  Is the name of the database role in the current database. role is a sysname, with no default.

• [ @membername= ] 'security_account'
  Is the security account being added to the role. security_account is a sysname, with no default. security_account can be a database user, database role, Windows login, or Windows group.

Return Code Values

0 (success) or 1 (failure)

Remarks

A member added to a role by using sp_addrolemember inherits the permissions of the role. If the new member is a Windows-level principal without a corresponding database user, a database user will be created but may not be fully mapped to the login. Always check that the login exists and has access to the database.

A role cannot include itself as a member. Such "circular" definitions are not valid, even when membership is only indirectly implied by one or more intermediate memberships.

sp_addrolemember cannot add a fixed database role, fixed server role, or dbo to a role. sp_addrolemember cannot be executed within a user-defined transaction.

Only use sp_addrolemember to add a member to a database role. To add a member to a server role, use sp_addsrvrolemember (Transact-SQL).

Permissions

Adding members to database user-defined roles requires one of the following:

• Membership in the db_securityadmin or db_owner fixed database role.

• Membership in the role that owns the role.

• ALTER ANY ROLE permission or ALTER permission on the role.

Adding members to fixed database roles requires membership in the db_owner fixed database role.

Examples

A. Adding a Windows login

USE AdventureWorks2008R2;
GO
CREATE USER Mary5 FOR LOGIN [Contoso\Mary5] ;
GO
EXEC sp_addrolemember 'Production', 'Mary5'

B. Adding a database user

EXEC sp_addrolemember 'Production', 'Mary5'

See Also

Reference