| title | sp_dropapprole (Transact-SQL) | ||
|---|---|---|---|
| description | sp_dropapprole removes an application role from the current database. | ||
| author | VanMSFT | ||
| ms.author | vanto | ||
| ms.reviewer | randolphwest | ||
| ms.date | 06/23/2025 | ||
| ms.service | sql | ||
| ms.subservice | system-objects | ||
| ms.topic | reference | ||
| f1_keywords |
|
||
| helpviewer_keywords |
|
||
| dev_langs |
|
[!INCLUDE SQL Server]
Removes an application role from the current database.
Important
[!INCLUDE ssNoteDepFutureAvoid] Use DROP APPLICATION ROLE instead.
:::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: Transact-SQL syntax conventions
sp_dropapprole [ @rolename = ] N'rolename'
[ ; ]
The application role to remove. @rolename is sysname, with no default. @rolename must exist in the current database.
0 (success) or 1 (failure).
sp_dropapprole can only be used to remove application roles. If a role owns any securables, the role can't be dropped. Before dropping an application role that owns securables, you must first transfer ownership of the securables, or drop them.
sp_dropapprole can't be executed within a user-defined transaction.
Requires ALTER ANY APPLICATION ROLE permission on the database.
The following example removes the SalesApp application role from the current database.
EXECUTE sp_dropapprole 'SalesApp';