DROP SESSION POLICY¶
Removes a session policy from the system.
- See also:
DROP SESSION POLICY [ IF EXISTS ] <name>
Identifier for the session 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¶
A role used to execute this SQL command must have the following privileges at a minimum:
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 session policy DDL and privileges, see Managing Session Policies.
Prior to dropping a session policy, execute the following statement to determine if any session policies are applied to accounts or users. For more information, see POLICY_REFERENCES.
SELECT * from table(information_schema.policy_references(policy_name=>'<string>'));
A session policy cannot be dropped successfully if it is currently attached to an account or user. Before executing a DROP statement, UNSET the session policy from the account with an ALTER ACCOUNT statement or unset the session policy from a user with an ALTER USER statement.
DROP SESSION POLICY session_policy_production_1;