> ## 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 SQLCatalog databases, schemas, and managed topic sources are named.

StreamNative maps SQLCatalog and topic names to identifiers in the SQLWorkspace engine.

## SQLCatalog and topic mapping

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

StreamNative preserves mapped database, schema, and topic names when they fit the SQLWorkspace engine's 63-byte identifier limit. Longer names are shortened and receive a deterministic suffix. 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 SQLWorkspace engine. Quoting preserves case and avoids conflicts with SQL keywords or punctuation.

For more information about sources, tables, and materialized views, see [RisingWave SQL reference](/sql/overview/engine/risingwave).