drop role

Syntax

drop role role_name [with override]

role_name – is the name of the role you want to drop.
with override – overrides any restrictions on dropping a role. When you use the with override option, you can drop any role without having to check whether the role permissions have been dropped in each database.

Example 1 – Drops the named role only if all permissions in all databases have been revoked. The system administrator or object owner must revoke permissions granted in each database before dropping a role, or the command fails:
```
drop role doctor_role
```
Example 2 – Drops the named role and removes permission information and any other reference to the role from all databases:
```
drop role doctor_role with override
```

You need not drop memberships before dropping a role. Dropping a role automatically removes any user’s membership in that role, regardless of whether you use the with override option.
Use drop role from the master database.
All rows corresponding to a dropped role are removed from the syspasswordhistory table.

You cannot use drop role to drop system roles.

See also sp_activeroles, sp_displaylogin, sp_displayroles, sp_helprotect in Reference Manual: Procedures.

ANSI SQL – Compliance level: Transact-SQL extension.

The permission checks for drop role differ based on your granular permissions settings.

Setting	Description
Enabled	With granular permissions enabled, you must be a user with `manage roles` privilege.
Disabled	With granular permissions disabled, you must be a user with sso_role.

Values in event and extrainfo columns of sysaudits are:

Information	Values
Event	85
Audit option	roles
Command or access audited	create role, drop role, alter role, grant role, or revoke role
Information in `extrainfo`	Roles – current active roles Keywords or options – NULL Previous value – NULL Current value – NULL Other information – NULL Proxy information – original login name, if set proxy is in effect