DROP <object>¶

Syntax¶

DROP <object_type> [ IF EXISTS ] <identifier>  [ CASCADE | RESTRICT ]

For specific syntax, usage notes, and examples, see:

Organization Objects:

• DROP ACCOUNT

Account Objects:

• DROP APPLICATION

• DROP APPLICATION PACKAGE

• DROP AUTHENTICATION POLICY

• DROP CATALOG INTEGRATION

• DROP COMPUTE POOL

• DROP CONNECTION

• DROP DATABASE

• DROP DATABASE ROLE

• DROP EXTERNAL VOLUME

• DROP INTEGRATION

• DROP NETWORK POLICY

• DROP RESOURCE MONITOR

• DROP ROLE

• DROP SHARE

• DROP USER

• DROP WAREHOUSE

Database Objects:

• DROP AGGREGATION POLICY

• DROP ALERT

• DROP AUTHENTICATION POLICY

• DROP DYNAMIC TABLE

• DROP EXTERNAL TABLE

• DROP FILE FORMAT

• DROP FUNCTION

• DROP GIT REPOSITORY

• DROP ICEBERG TABLE

• DROP IMAGE REPOSITORY

• DROP INDEX

• DROP MASKING POLICY

• DROP MATERIALIZED VIEW

• DROP MODEL

• DROP NETWORK RULE

• DROP PACKAGES POLICY

• DROP PASSWORD POLICY

• DROP PIPE

• DROP PROCEDURE

• DROP PROJECTION POLICY

• DROP ROW ACCESS POLICY

• DROP SCHEMA

• DROP SECRET

• DROP SEQUENCE

• DROP SERVICE

• DROP SESSION POLICY

• DROP SNAPSHOT

• DROP STAGE

• DROP STREAM

• DROP STREAMLIT

• DROP TABLE

• DROP TAG

• DROP TASK

• DROP VIEW

Classes:

• DROP SNOWFLAKE.ML.ANOMALY_DETECTION

• DROP BUDGET

• DROP CUSTOM_CLASSIFIER

• DROP SNOWFLAKE.ML.FORECAST

General Usage Notes¶

• The DROP command can include an IF EXISTS clause. If specified and the target object does not exist, the command does not return an error and completes successfully.

• The CASCADE | RESTRICT parameters apply only to databases, schemas, and tables, and is used to specify whether the object can be dropped if foreign keys that reference the object exist:

  • CASCADE drops the object, along with all the foreign keys that reference the object.

  • RESTRICT returns a warning and does not drop the object.

Examples¶

DROP DATABASE mydb;

DROP DATABASE IF EXISTS mydb;

DROP DATABASE IF EXISTS mydb RESTRICT;

DROP DATABASE IF EXISTS mydb CASCADE;