DROP ALERT¶

Drops an existing alert.

Tip

You can also use the Snowflake REST APIs to perform this operation. For information, see Delete an alert (REST endpoint reference).

See also:: CREATE ALERT , ALTER ALERT, DESCRIBE ALERT , SHOW ALERTS , EXECUTE ALERT

Syntax¶

DROP ALERT [ IF EXISTS ] <name>

Copy

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.

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).

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.

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.