Export (0) Print
Expand All
Expand Minimize
This topic has not yet been rated - Rate this topic

DROP APPLICATION ROLE (Transact-SQL)

Removes an application role from the current database.

Topic link iconTransact-SQL Syntax Conventions


DROP APPLICATION ROLE rolename
rolename

Specifies the name of the application role to be dropped.

If the application role owns any securables it cannot be dropped. Before dropping an application role that owns securables, you must first transfer ownership of the securables, or drop them.

Caution noteCaution

Beginning with SQL Server 2005, the behavior of schemas changed. As a result, code that assumes that schemas are equivalent to database users may no longer return correct results. Old catalog views, including sysobjects, should not be used in a database in which any of the following DDL statements have ever been used: CREATE SCHEMA, ALTER SCHEMA, DROP SCHEMA, CREATE USER, ALTER USER, DROP USER, CREATE ROLE, ALTER ROLE, DROP ROLE, CREATE APPROLE, ALTER APPROLE, DROP APPROLE, ALTER AUTHORIZATION. In such databases you must instead use the new catalog views. The new catalog views take into account the separation of principals and schemas that was introduced in SQL Server 2005. For more information about catalog views, see Catalog Views (Transact-SQL).

Requires ALTER ANY APPLICATION ROLE permission on the database.

Drop application role "weekly_ledger" from the database.

DROP APPLICATION ROLE weekly_ledger;
GO
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.