DROP CATALOG INTEGRATION¶
Removes a catalog integration from the account.
Syntax¶
Parameters¶
nameSpecifies the identifier for the catalog integration 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 (for example,
"My Catalog").
Access control requirements¶
A role used to execute this operation must have the following privileges at a minimum:
| Privilege | Object | Notes |
|---|---|---|
| OWNERSHIP | Integration (catalog) | 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](/sql-reference/sql/grant-ownership) command to a different role by the owning role (or any role with the MANAGE GRANTS privilege). |
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¶
- Dropped catalog integrations cannot be recovered; they must be recreated.
- When the IF EXISTS clause is specified and the target object doesn’t exist, the command completes successfully without returning an error.
-
You can’t drop or replace a catalog integration if one or more Apache Iceberg™ tables are associated with the catalog integration.
To view the tables that depend on a catalog integration, you can use the SHOW ICEBERG TABLES command and a query using the pipe operator (
->>) that filters on thecatalog_namecolumn.Note
The column identifier (
catalog_name) is case-sensitive. Specify the column identifier exactly as it appears in the SHOW ICEBERG TABLES output.For example:
Examples¶
Drop a catalog integration:
Drop the catalog integration again, but don’t raise an error if the integration doesn’t exist: