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

# Defining view name generation for database connections

> Control how Omni generates view names from database tables by always including catalog and schema prefixes.

Omni generates view names from your database tables, optionally including catalog and schema prefixes. The **Always Scope View Names** connection setting forces Omni to include catalog and schema prefixes for all tables, rather than only for tables outside the default catalog or schema. This produces predictable, fully-qualified view names across your model — useful when you work with multiple catalogs or schemas.

The setting is enabled by default for connections created on or after April 30, 2026 to supported databases. Older connections have it disabled for backward compatibility — see [Existing connections](#existing-connections) for more information.

## Supported databases

This setting is only available for databases that support multiple catalogs: [Athena](/connect-data/setup/), [Databricks](/connect-data/setup/databricks), Databricks Lakebase, [Postgres](/connect-data/setup/postgres), [Redshift](/connect-data/setup/redshift), [Snowflake](/connect-data/setup/snowflake), and Trino.

## How view naming works

Without this setting enabled, Omni generates view names differently depending on whether a table is in the default catalog and schema:

| Setup                                | View name in Omni           |
| ------------------------------------ | --------------------------- |
| default catalog + default schema     | `<table>`                   |
| default catalog + non-default schema | `<schema>__<table>`         |
| non-default catalog + any schema     | `<catalog_schema>__<table>` |

With **Always Scope View Names** enabled, all views include the full catalog and schema prefix:

| Setup                                | View name in Omni           |
| ------------------------------------ | --------------------------- |
| default catalog + default schema     | `<catalog_schema>__<table>` |
| default catalog + non-default schema | `<catalog_schema>__<table>` |
| non-default catalog + any schema     | `<catalog_schema>__<table>` |

## When to use this setting

Enable this setting when you want:

* **Consistent naming** across all views, regardless of catalog or schema location
* **Predictable references** when working with multiple catalogs or schemas

Additionally, this setting can be useful for single catalog connections as it will create shorter, more convenient view names for references.

## Enabling or disabling the setting

<Note>
  **Connection Admin** permissions are required to modify connection settings.
</Note>

### New connections

Connections created **after** the setting was introduced (**April 30, 2026**) have the setting enabled by default. You can disable it while setting up the connection, if needed.

### Existing connections

Connections created **before** this setting was introduced (**April 30, 2026**) have it disabled by default to preserve backward compatibility.

<Warning>
  After the next schema refresh, every view from the connection's default catalog will be renamed in the schema model. Workbooks, dashboards, queries, and shared models that reference the current view names will break and need to be updated.
</Warning>

To enable the setting for an existing connection:

<Steps>
  <Step title="Open the connection details" noAnchor>
    1. Navigate to **Settings > Connections**.
    2. Click a connection.
    3. Locate the **Always Scope View Names** toggle in the connection settings.
  </Step>

  <Step title="Toggle the setting" noAnchor>
    1. Click the **Always Scope View Names** toggle to enable the setting.
    2. When prompted, confirm the change.
  </Step>

  <Step title="Save & apply the changes" noAnchor>
    1. When finished, click **Update and Test connection**.
    2. Trigger a [**schema refresh**](/modeling/develop/schema-refreshes) to apply the changes to your Omni model.
  </Step>

  <Step title="Update model references" noAnchor>
    After the schema refresh completes, you'll need to update references to the views in the shared model and any content built on the shared model.

    Use the [Content Validator](/modeling/develop/content-validator) to identify and fix broken references in your documents and workbooks.
  </Step>
</Steps>

## Next steps

* Learn how to [refresh your schema](/modeling/develop/schema-refreshes) to apply connection changes
* Understand how [view names](/modeling/views/parameters/name) work in Omni's model
* Use the [Content Validator](/modeling/develop/content-validator) to identify broken model references in your content