DROP DATA MOVEMENT POLICY

Removes a data movement policy from the current/specified schema.

See also:

CREATE DATA MOVEMENT POLICY , ALTER DATA MOVEMENT POLICY , DESCRIBE DATA MOVEMENT POLICY , SHOW DATA MOVEMENT POLICIES

CREATE DATA MOVEMENT RULE , ALTER DATA MOVEMENT RULE , DROP DATA MOVEMENT RULE

Syntax

DROP DATA MOVEMENT POLICY [ IF EXISTS ] <name>

Parameters

name

Specifies the identifier for the data movement 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:

PrivilegeObjectNotes
OWNERSHIPData movement policyOWNERSHIP is a special privilege on an object that is automatically granted to the role that created the object, but can also be transferred using the GRANT OWNERSHIP command to a different role by the owning role (or any role with the MANAGE GRANTS privilege).

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 data movement policy can’t be dropped while it’s attached to a tag or the account. Before you drop the policy, detach it with an ALTER TAG or ALTER ACCOUNT statement that unsets the data movement policy.
  • When the IF EXISTS clause is specified and the target object doesn’t exist, the command completes successfully without returning an error.

Examples

Drop a data movement policy:

DROP DATA MOVEMENT POLICY hr_pii_dmp;