Skip to main content
This guide applies to the Included schemas field in the connection settings page. For the modeling parameter, which restricts the schemas that are accessible in workbooks, refer to the included_schemas reference.
When a database connection includes many schemas, your Omni model can become larger than necessary. Restricting which schemas are included helps improve performance, reduces clutter, and ensures only relevant data is modeled.

​
Requirements

Connection Admin permissions are required to modify connection settings.

​
Defining included schemas

You can control which schemas Omni pulls into your model using the Include schemas field in the connection settings. Only the listed schemas will be included when the model is built. If this field is left blank, Omni will include all available schemas in the accessible databases for that connection. When finished modifying the connection settings, trigger a schema refresh to apply the changes to the model.

​
Example configuration

The Include schemas field accepts a comma-separated list of schema names, and also supports wildcard syntax for partial matches.
The values in Included schemas are case-sensitive, meaning they must exactly match the name of the schema in the database.
Include only the blob_sales schema
blob_sales
Include only the blob_sales & blob_marketing schemas
blob_sales, blob_marketing
Include only schemas starting with blob_
blob_*