| title | sp_dropapprole (Transact-SQL) | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 03/14/2017 | ||
| ms.prod | sql-non-specified | ||
| ms.reviewer | |||
| ms.suite | |||
| ms.technology |
|
||
| ms.tgt_pltfrm | |||
| ms.topic | language-reference | ||
| f1_keywords |
|
||
| dev_langs |
|
||
| helpviewer_keywords |
|
||
| ms.assetid | ea1aefe6-8f7d-46e9-a3cb-7b037b393e73 | ||
| caps.latest.revision | 28 | ||
| author | BYHAM | ||
| ms.author | rickbyh | ||
| manager | jhubbard |
[!INCLUDEtsql-appliesto-ss2008-xxxx-xxxx-xxx_md]
Removes an application role from the current database.
Important
[!INCLUDEssNoteDepFutureAvoid] Use DROP APPLICATION ROLE instead.
| Applies to: [!INCLUDEssNoVersion] ([!INCLUDEssKatmai] through current version). |
Transact-SQL Syntax Conventions
sp_dropapprole [@rolename = ] 'role'
[ @rolename = ] 'role'
Is the application role to remove. role is a sysname, with no default. role 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 cannot be dropped. Before dropping an application role that owns securables, you must first transfer ownership of the securables, or drop them.
sp_dropapprole cannot 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.
EXEC sp_dropapprole 'SalesApp';
Security Stored Procedures (Transact-SQL)
sp_addapprole (Transact-SQL)
DROP APPLICATION ROLE (Transact-SQL)
sp_changeobjectowner (Transact-SQL)
sp_setapprole (Transact-SQL)
System Stored Procedures (Transact-SQL)