DROP AGGREGATION POLICY¶
Removes an aggregation policy from the current/specified schema.
- See also:
Syntax¶
DROP AGGREGATION POLICY <name>
Parameters¶
name
Specifies the identifier for the aggregation 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 |
Aggregation 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 aggregation policy DDL and privileges, see Privileges and commands.
Usage notes¶
Prior to dropping the aggregation policy, execute the following statement to determine if the aggregation policy is set on any tables or views.
SELECT * FROM TABLE(mydb.INFORMATION_SCHEMA.POLICY_REFERENCES(POLICY_NAME=>'my_agg_policy'));
For more information, see Identify aggregation policy references.
An aggregation policy cannot be dropped successfully if it is currently assigned to a table or view.
Before executing a DROP statement, detach the aggregation policy from the table or view with an ALTER TABLE or ALTER VIEW statement.
Example¶
Drop the aggregation policy:
DROP AGGREGATION POLICY my_aggpolicy;