doc/user/content/sql/drop-connection.md
DROP CONNECTION removes a connection from Materialize. If there are sources
depending on the connection, you must explicitly drop them first, or use the
CASCADE option.
DROP CONNECTION [IF EXISTS] <connection_name> [CASCADE|RESTRICT];
| Syntax element | Description |
|---|---|
| IF EXISTS | Optional. If specified, do not return an error if the specified connection does not exist. |
connection_name> | The connection you want to drop. For available connections, see SHOW CONNECTIONS. |
| CASCADE | Optional. If specified, remove the connection and its dependent objects. |
| RESTRICT | Optional. Do not drop the connection if it has dependencies. (Default) |
To drop an existing connection, run:
DROP CONNECTION kafka_connection;
To avoid issuing an error if the specified connection does not exist, use the IF EXISTS option:
DROP CONNECTION IF EXISTS kafka_connection;
If the connection has dependencies, Materialize will throw an error similar to:
DROP CONNECTION kafka_connection;
ERROR: cannot drop materialize.public.kafka_connection: still depended upon by catalog item
'materialize.public.kafka_source'
, and you'll have to explicitly ask to also remove any dependent objects using the CASCADE option:
DROP CONNECTION kafka_connection CASCADE;
The privileges required to execute this statement are:
{{% include-headless "/headless/sql-command-privileges/drop-connection" %}}