DROP FEATURE POLICY¶

Removes the specified feature policy. For an overview, see Feature policies.

See also:: CREATE FEATURE POLICY , ALTER FEATURE POLICY, DESCRIBE FEATURE POLICY, SHOW FEATURE POLICIES

Syntax¶

DROP FEATURE POLICY <name>

Parameters¶

name: Specifies the identifier for the feature policy to drop.

If the identifier contains spaces or special characters, the entire string must be enclosed in double quotes. Identifiers enclosed in double quotes are also case-sensitive.

For more information, see Identifier requirements.

Access control requirements¶

A role used to execute this operation must have the following privileges at a minimum:

Privilege	Object	Notes
OWNERSHIP	Feature policy	This privilege is required to drop a feature policy.

Operating on an object in a schema requires at least one privilege on the parent database and at least one privilege on the parent schema.

For instructions on creating a custom role with a specified set of privileges, see Creating custom roles.

For general information about roles and privilege grants for performing SQL actions on securable objects, see Overview of Access Control.

Usage Notes¶

A feature policy can’t be dropped if it’s currently applied to an object. First un-apply the feature policy using ALTER ACCOUNT (for account-level bindings) or ALTER APPLICATION (for app-level bindings), then drop the feature policy.

Examples¶

The following example drops the feature policy named block_db_policy:

DROP FEATURE POLICY block_db_policy;

+---------------------------------------+
| status                                |
|---------------------------------------|
| BLOCK_DB_POLICY successfully dropped. |
+---------------------------------------+