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

# Snowflake semantic view limitations

> What Omni doesn't import from a Snowflake semantic view, and what imports in a fixed way.

Omni imports most of a Snowflake semantic view definition. This page lists the parts that don't import, and the parts that import in a fixed way. If you need one of these, reach out to Omni support.

## Verified queries aren't imported

Verified queries defined on a semantic view don't import. The generated topic has no [`sample_queries`](/modeling/topics/parameters/sample-queries).

## Relationships always import as `many_to_one`

Snowflake doesn't expose the cardinality of a relationship, so every relationship imports with [`relationship_type: many_to_one`](/modeling/relationships/parameters/relationship-type) from the foreign-key table to the referenced table.

## ASOF and RANGE relationships aren't imported

`ASOF` and `RANGE` relationships aren't imported. The topic imports without those joins. A view left with no relationship to the rest of the topic gets a [validation warning](/connect-data/snowflake-semantic-views/sync/trigger-sync#troubleshooting).

## Topics don't follow dbt virtual schemas

Semantic view topics query the tables named in the semantic view's definition, so switching your dbt environment doesn't change what they read. Use [`included_schemas`](/modeling/models/included-schemas) to import from your production schema only. Topics can't follow [dbt virtual schemas](/integrations/dbt/virtual-schemas).

## Next steps

* Learn [what Omni creates for each semantic view](/connect-data/snowflake-semantic-views/sync/trigger-sync)
* See [what each part of a definition becomes in Omni](/connect-data/snowflake-semantic-views/sync/metadata-reference)
* [Query a semantic view topic](/connect-data/snowflake-semantic-views/querying)