DROP CODE BUNDLE

Removes the specified Code Bundle from the current or specified schema, including all of its versions.

See also:

CREATE CODE BUNDLE, ALTER CODE BUNDLE, DESCRIBE CODE BUNDLE, SHOW CODE BUNDLES

Syntax

DROP CODE BUNDLE [ IF EXISTS ] <name>

Parameters

name

Specifies the identifier of the Code Bundle 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.

For more information, see Identifier requirements.

IF EXISTS

Doesn’t return an error if the Code Bundle doesn’t exist.

Access control requirements

A role used to execute this operation must have the following privileges at a minimum:

PrivilegeObjectNotes
OWNERSHIPCode BundleOWNERSHIP 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).

Operating on an object in a schema requires at least one privilege on the parent database and at least one privilege on the parent 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

  • Tasks and other code that run the dropped Code Bundle by name fail after it’s dropped. Drop or update those tasks first.
  • Dropping a Code Bundle doesn’t delete the stage or workspace that it was created from.

Examples

Drop a Code Bundle:

DROP CODE BUNDLE my_db.my_schema.my_bundle;

Drop a Code Bundle without an error if it doesn’t exist:

DROP CODE BUNDLE IF EXISTS my_db.my_schema.my_bundle;