> ## 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.

# SQL Workspaces Naming Rules

> Understand how SQL Catalog databases, schemas, and managed topic sources are named.

StreamNative maps SQL Catalog and topic names to identifiers in the SQL Workspace engine.

## SQL Catalog and topic mapping

| Source system | Database | Schema | Source |
| - | - | - | - |
| Pulsar | SQL Catalog name | Full Pulsar tenant and namespace, such as `public/default` | Local topic name |
| Kafka | SQL Catalog name | `public` | Kafka topic name |

Long database, schema, and topic names might be shortened when they are mapped to engine identifiers. Use the exact schema and source names shown in SQL Studio.

## Quoted identifiers

Always enclose topic-derived schema and source names in double quotes, including names that do not contain punctuation:

```sql theme={null}
SELECT * FROM "public/default"."order-events";
SELECT * FROM "public"."events.production";
```

Double quotes identify SQL objects. Single quotes represent string values and cannot be used in place of identifier quotes.

Unquoted identifiers are normalized by the SQL Workspace engine. Quoting preserves case and avoids conflicts with SQL keywords or punctuation.

For more information about sources, tables, and materialized views, see [Source, Table, Materialized View, and Sink](https://docs.risingwave.com/get-started/source-table-mv-sink) in the RisingWave documentation.


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