REVOKE XML Schema Collection Permissions (Transact-SQL)

Syntax

REVOKE [ GRANT OPTION FOR ] permission [ ,...n ] ON 
    XML SCHEMA COLLECTION :: [ schema_name . ]
    XML_schema_collection_name
    { TO | FROM } <database_principal> [ ,...n ]
        [ CASCADE ]
    [ AS <database_principal> ] 

<database_principal> ::= 
        Database_user 
    | Database_role 
    | Application_role 
    | Database_user_mapped_to_Windows_User 
    | Database_user_mapped_to_Windows_Group 
    | Database_user_mapped_to_certificate 
    | Database_user_mapped_to_asymmetric_key 
    | Database_user_with_no_login 

Arguments

• permission
  Specifies a permission that can be revoked on an XML schema collection. For a list of the permissions, see the Remarks section later in this topic.

• ON XML SCHEMA COLLECTION :: [ schema_name**.** ] XML_schema_collection_name
  Specifies the XML schema collection on which the permission is being revoked. The scope qualifier (::) is required. If schema_name is not specified, the default schema will be used. If schema_name is specified, the schema scope qualifier (.) is required.

• GRANT OPTION
  Indicates that the right to grant the specified permission to other principals will be revoked. The permission itself will not be revoked.

  Important

  If the principal has the specified permission without the GRANT option, the permission itself will be revoked.

• CASCADE
  Indicates that the permission being revoked is also revoked from other principals to which it has been granted or denied by this principal.

  Warning

  A cascaded revocation of a permission granted WITH GRANT OPTION will revoke both GRANT and DENY of that permission.

• { TO | FROM } <database_principal>
  Specifies the principal from which the permission is being revoked.

• AS <database_principal>
  Specifies a principal from which the principal executing this query derives its right to revoke the permission.

• Database_user
  Specifies a database user.

• Database_role
  Specifies a database role.

• Application_role
  Specifies an application role.

• Database_user_mapped_to_Windows_User
  Specifies a database user mapped to a Windows user.

• Database_user_mapped_to_Windows_Group
  Specifies a database user mapped to a Windows group.

• Database_user_mapped_to_certificate
  Specifies a database user mapped to a certificate.

• Database_user_mapped_to_asymmetric_key
  Specifies a database user mapped to an asymmetric key.

• Database_user_with_no_login
  Specifies a database user with no corresponding server-level principal.

Remarks

Information about XML schema collections is visible in the sys.xml_schema_collections catalog view.

The statement will fail if CASCADE is not specified when you are revoking a permission from a principal that was granted that permission with GRANT OPTION specified.

An XML schema collection is a schema-level securable contained by the schema that is its parent in the permissions hierarchy. The most specific and limited permissions that can be revoked on an XML schema collection are listed in the following table, together with the more general permissions that include them by implication.

Permissions

Requires CONTROL permission on the XML schema collection. If you use the AS option, the specified principal must own the XML schema collection.

Examples

The following example revokes EXECUTE permission on the XML schema collection Invoices4 from the user Wanida. The XML schema collection Invoices4 is located inside the Sales schema of the AdventureWorks2008R2 database.

USE AdventureWorks2008R2;

REVOKE EXECUTE ON XML SCHEMA COLLECTION::Sales.Invoices4 FROM Wanida;

GO

See Also

Reference

Concepts