> ## Documentation Index
> Fetch the complete documentation index at: https://docs.streamnative.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Add a SQL Catalog in the Cloud Console

> Connect a StreamNative Pulsar or Kafka cluster to a SQL Workspace as a SQL Catalog.

Add a StreamNative Pulsar or Kafka cluster to a ready SQL Workspace. Each SQL Catalog appears as a database in the SQL Workspace engine.

## Before you begin

You need:

* A **Ready** SQL Workspace.
* A Pulsar or Kafka cluster in the same organization.
* A cloud role that permits SQL Catalog management.

## Add a catalog

1. In the Cloud Console, click **SQL**.
2. Open the workspace selector and click **Manage workspaces**.
3. Open the action menu for the target workspace and click **Manage**.
4. In the **Databases** section, click **Import clusters**.
5. Select an instance.
6. Select one or more Pulsar or Kafka clusters.
7. Confirm the database name for each selected cluster.
8. Click **Import**.
9. Wait until each imported database reports **Ready**.

<Frame caption="Open workspace management to view SQL Workspaces.">
  <img src="https://mintcdn.com/streamnative/rWIjiXpwX0pKVnS4/media/sql-workspaces-list.png?fit=max&auto=format&n=rWIjiXpwX0pKVnS4&q=85&s=00c2c2dce1ddc9cf8ddb158651c5fdc6" alt="SQL Workspaces page in the StreamNative Cloud Console" width="4872" height="2182" data-path="media/sql-workspaces-list.png" />
</Frame>

<Frame caption="Open the action menu and manage the target SQL Workspace.">
  <img src="https://mintcdn.com/streamnative/rWIjiXpwX0pKVnS4/media/sql-workspace-manage.png?fit=max&auto=format&n=rWIjiXpwX0pKVnS4&q=85&s=7afaaf53b702e1e0ffc78d6a7854d461" alt="Manage action in the SQL Workspace menu" width="4518" height="994" data-path="media/sql-workspace-manage.png" />
</Frame>

<Frame caption="Import Pulsar or Kafka clusters as SQL Catalogs.">
  <img src="https://mintcdn.com/streamnative/rWIjiXpwX0pKVnS4/media/sql-workspace-add-sqlcatalog.png?fit=max&auto=format&n=rWIjiXpwX0pKVnS4&q=85&s=0278d532d84f7aea5ffea8f8f80a0d53" alt="Import clusters action for a SQL Workspace" width="5002" height="2328" data-path="media/sql-workspace-add-sqlcatalog.png" />
</Frame>

## What happens next

StreamNative creates a database for each SQL Catalog, periodically discovers eligible topics, and creates missing source objects in that database. Refer to topic-derived schemas and sources with double-quoted identifiers. This Pulsar example uses the `public/default` namespace; Kafka sources use the `public` schema.

```sql theme={null}
SELECT *
FROM "public/default"."orders-topic"
LIMIT 100;
```

Create the tables or materialized views needed for subsequent transformations and continuous processing. For details, see [SQL Catalog](/sql/overview/sqlcatalog).

Removing the SQL Catalog later stops topic discovery and stops its managed sources from consuming newly published records. Data already ingested or processed by the SQL Workspace engine is retained, and the source cluster and its topics are not deleted. See [Data Retention](/sql/operations/data-retention).

Next, [query with SQL Studio](/sql/get-started/console/query-sql-studio) or [connect with a PostgreSQL client](/sql/get-started/console/connect-postgresql-client).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.