DROP MASKING POLICY¶
Removes a masking policy from the system.
- See also:
DROP MASKING POLICY <name>
Identifier for the masking policy; must be unique for your account.
The identifier value must start with an alphabetic character and cannot contain spaces or special characters unless the entire identifier string is enclosed in double quotes (e.g.
"My object"). Identifiers enclosed in double quotes are also case-sensitive.
For more details, see Identifier requirements.
Access control requirements¶
OWNERSHIP 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).
Note that operating on any object in a schema also requires the USAGE privilege on the parent database and schema.
For instructions on creating a custom role with a specified set of privileges, see Creating custom roles.
For additional details on masking policy DDL and privileges, see Managing Column-level Security.
Prior to dropping a masking policy, execute the following statement to determine if any masking policies are applied to columns. For more information, see POLICY_REFERENCES.
SELECT * from table(information_schema.policy_references(policy_name=>'<string>'));
A masking policy cannot be dropped successfully if it is currently assigned to a column or a tag.
Before executing a DROP statement, UNSET the masking policy from the column with an ALTER TABLE … ALTER COLUMN or ALTER VIEW statement, and, if necessary, unset the masking policy from the tag using an ALTER TAG statement.
DROP MASKING POLICY ssn_mask;