DROP STAGE¶

Removes the specified named internal or external stage from the current/specified schema. The status of the files in the stage depends on the stage type:

• For an internal stage, all of the files in the stage become unavailable along with the dropped stage, regardless of their load status. The files remain recoverable while the stage is within its retention period: if you restore the stage with UNDROP STAGE, the staged files are restored with it. After the retention period passes, the files are removed permanently.
• For an external stage, only the stage itself is dropped; any data files in the referenced external location (Amazon S3, Google Cloud Storage, or Microsoft Azure) are not removed.

See also:

CREATE STAGE , ALTER STAGE , UNDROP STAGE , SHOW STAGES , DESCRIBE STAGE

Syntax¶

DROP STAGE [ IF EXISTS ] <name>

Parameters¶

name

Specifies the identifier for the stage to drop. If the identifier contains spaces, special characters, or mixed-case characters, the entire string must be enclosed in double quotes. Identifiers enclosed in double quotes are also case-sensitive.

Usage notes¶

• To restore a dropped stage, use UNDROP STAGE within the stage’s retention period. After that period passes, the stage must be recreated.
• This command cannot be used to drop the stage associated with a table or user; only named stages (internal or external) can be dropped.

Examples¶

Copy code

DROP STAGE my_stage;

--------------------------------+
             status             |
--------------------------------+
 MY_STAGE successfully dropped. |
--------------------------------+