DROP BACKUP SET¶
Deletes a backup set.
- See also:
Syntax¶
DROP BACKUP SET <name>
Parameters¶
nameSpecifies the identifier for the backup set.
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.
For more information, see 식별자 요구 사항.
Access control requirements¶
A role used to execute this operation must have the following privileges at a minimum:
Privilege |
Object |
Notes |
|---|---|---|
OWNERSHIP |
Backup set |
The role used to modify the backup policy for a backup set must have the OWNERSHIP privilege on the set. |
For instructions on creating a custom role with a specified set of privileges, see 사용자 지정 역할 만들기.
For general information about roles and privilege grants for performing SQL actions on securable objects, see 액세스 제어의 개요.
Usage notes¶
중요
If the backup policy has a retention lock applied to it, and there are any unexpired backups in the backup set, then you can’t delete the backup set. In that case, you must wait for all the backups in the set to expire. This restriction applies even to privileged roles such as ACCOUNTADMIN, and to Snowflake support. For that reason, be careful when specifying retention lock and a long expiration period in a backup policy.
You also can’t drop a backup set if any of the backups it contains have a legal hold applied.
Examples¶
Delete the backup set t1_backups:
DROP BACKUP SET t1_backups;