DROP DATA MOVEMENT RULE

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

See also:

CREATE DATA MOVEMENT RULE , ALTER DATA MOVEMENT RULE , SHOW DATA MOVEMENT RULES , DESCRIBE DATA MOVEMENT RULE

CREATE DATA MOVEMENT POLICY , ALTER DATA MOVEMENT POLICY , DROP DATA MOVEMENT POLICY

Syntax

DROP DATA MOVEMENT RULE [ IF EXISTS ] <name>

Parameters

name

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

  • When the IF EXISTS clause is specified and the target object doesn’t exist, the command completes successfully without returning an error.
  • A data movement rule that’s currently referenced by a data movement policy can’t be dropped. Remove the rule from the policy’s ENFORCE_RULES or ALERT_RULES before you drop it.

Examples

Drop a data movement rule:

DROP DATA MOVEMENT RULE hr_pii_copy_guard;