Azure DevOps
GitHub
GitLab
Next steps
After you successfully connect your dbt repository, you need to:- Configure your production dbt environment
- Sync dbt with Omni
- Set up Virtual Schemas. This isn’t required to use the dbt integration, but enabling Virtual Schemas before you start building in Omni avoids migrating later.
Common questions
What features require a direct dbt Git repository connection?
What features require a direct dbt Git repository connection?
While reading metadata from your database provides basic descriptions, you won’t be able to:
- Push SQL changes or new fields created in Omni back to dbt
- Sync personal development branches in Omni to your development dbt environment
- Auto-generate primary keys and relationships from dbt YAML constraints
Can I use the same Git repo for Omni models and dbt code?
Can I use the same Git repo for Omni models and dbt code?
Omni strongly recommends using two separate repositories: one for your dbt project and one for your Omni semantic model. This gives you:
- Clear ownership — Separates data engineering from business logic.
- Faster iteration — Prevents semantic refreshes from being tied to dbt compilation times.
- Cleaner Git history — Keeps automatic commits from the Omni IDE out of your dbt pull requests.
- Coordinated deployments — Ensures Omni model changes only apply after related dbt runs complete, so downstream content doesn’t break.
Can I use the same dbt repository for multiple database connections?
Can I use the same dbt repository for multiple database connections?
Yes. This is common when using different credentials for different environments, such as using separate Snowflake accounts for different departments.
You must configure dbt settings and environment variables for each individual connection to ensure models map to the correct database and schema.
Does Omni support dbt mesh architecture across separate Git repositories?
Does Omni support dbt mesh architecture across separate Git repositories?
No. Currently, Omni supports one dbt repository per database connection. If your architecture relies on multiple interconnected projects in separate repositories, Omni cannot ingest all projects into a single connection at this time.