DROP JOIN POLICY¶

Removes a join policy from the current/specified schema.

See also:: Join policy DDL reference

Syntax¶

DROP JOIN POLICY <name>

Copy

Parameters¶

name

Specifies the identifier for the join 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	Join 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).

The USAGE privilege on the parent database and schema are required to perform operations on any object in a 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 more information about join policy DDL and privileges, see Managing join policies.

Usage notes¶

Prior to dropping the join policy, execute the following statement to determine if the policy is set on any tables or views.
```
SELECT * FROM TABLE(mydb.INFORMATION_SCHEMA.POLICY_REFERENCES(POLICY_NAME=>'my_join_policy'));
```
Copy
For more information, see Getting information about tables and views attached to join policies.
A join policy cannot be dropped successfully if it is currently assigned to a table or view.

Before executing a DROP statement, detach the join policy from the table or view with an ALTER TABLE or ALTER VIEW statement.

Example¶

Drop a join policy:

DROP JOIN POLICY my_join_policy;

Copy