DROP PROJECTION POLICY¶

Removes a projection policy from the current/specified schema.

See also:: Projection policy DDL reference

Syntax¶

DROP PROJECTION POLICY <name>

Copy

Parameters¶

name

Specifies the identifier for the projection 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 SQL command must have the following privileges at a minimum:

Privilege	Object	Notes
OWNERSHIP	Projection policy	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 general information about roles and privilege grants for performing SQL actions on securable objects, see Overview of Access Control.

For additional details on projection policy DDL and privileges, see Privileges and commands.

Usage notes¶

Prior to dropping the projection policy, execute the following statement to determine if the projection policy is set on any columns.
```
SELECT * from table(mydb.information_schema.policy_references(policy_name=>'do_not_project'));
```
Copy
For more information, see Identify projection policy references.
A projection policy cannot be dropped successfully if it is currently assigned to a column.

Before executing a DROP statement, UNSET the projection policy from the column with an ALTER TABLE … ALTER COLUMN or an ALTER VIEW statement.

Example¶

Drop the projection policy:

DROP PROJECTION POLICY do_not_project;

Copy