DROP ALERT¶
Drops an existing alert.
Tip
In addition to SQL, you can also use other interfaces, such as Snowflake REST APIs, Snowflake Python APIs, and Snowflake CLI. See Alternate interfaces.
- See also:
CREATE ALERT , ALTER ALERT, DESCRIBE ALERT , SHOW ALERTS , EXECUTE ALERT
Syntax¶
DROP ALERT [ IF EXISTS ] <name>
Required parameters¶
name
Identifier for the alert 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.
Access control requirements¶
A role used to execute this SQL command must have the following privileges at a minimum:
Privilege |
Object |
Notes |
---|---|---|
OWNERSHIP |
Alert |
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.
Usage notes¶
When an alert is dropped, any current evaluation of the condition of the alert (i.e. a run with an EXECUTING state in the ALERT_HISTORY output) is completed.
An alert can be dropped by the alert owner (i.e. the role that has the OWNERSHIP privilege on the alert) or a higher role without first suspending the alert.
Examples¶
See Dropping an alert.
Alternate interfaces¶
Snowflake REST APIs
Delete an alert endpoint
Snowflake Python APIs
alert.AlertResource.drop method
Snowflake CLI
Not supported