Requirements
To follow the steps in this guide, you’ll need:- Organization Admin permissions in Omni
- Permissions in Postgres that allow you to create database users
Setup
1
Create an Omni database user
-
In your Postgres database, run the following command to create a database user for Omni:
Create Omni user
-
Grant permissions to the Omni user. If you’re using a schema other than
public, run the following to grant usage to Omni:Grant usage to the Omni user -
Lastly, ensure any tables created in the future will be accessible:
Grant permissions to future tables to the Omni user
2
Set up a table upload schema
import UploadSchemaCallout from “/snippets/connect-data/upload-schema-callout.mdx”;In this step, you’ll create a dedicated schema to use for table uploads. This schema can’t be used for other modeled tables.
- Create the schema in Postgres.
-
Run the following commands to grant the Omni user the required privileges:
Grant Omni user permissions to upload schema
3
Allowlist Omni's IP addresses
If access to the Postgres database is limited by IP address, you’ll need to add Omni’s IPs to the allowlist before you create the database connection.Omni’s IP addresses can be found on an individual connection’s page, accessed by navigating to Settings > Connections and clicking a connection.
4
Create the connection in Omni
- In Omni, click Settings > Connections.
- Click the Postgres option.
-
On the connection setup page, fill in the connection details:
Name Required? Description Display Name Yes A user-friendly name for the connection, which will be used throughout Omni Host Yes The hostname or IP address of the database server Port Yes The port number for the database connection. Defaults to 5432. Database Yes The database to connect to Include Schemas No A Comma-separated list of schemas to include in the connection Offloaded Schemas No A comma-separated list of schemas to include in the connection, which will only load on demand. This setting is good for very large schemas or dbt dev schemas. Schema for Table Uploads No The name of the schema to use for table (CSV) uploads. If left blank, you can upload tables but they won’t be pushed to the database or be available for use in joins. Username Yes The username for database authentication Password Yes The password for database authentication Database Timezone Yes The timezone used by the database Query Timezone Yes The timezone to use for Omni queries. If a timezone is specified, data will be converted from the Database timezone to the selected timezone. Allow User-Specific Timezones No When enabled, users can override the connection timezone with their own when querying Query Timeout No Maximum time in seconds before a query times out Infer Relationships from Foreign Keys No When enabled, Omni will automatically infer relationships between tables based on foreign key constraints in the database - When finished, click Create connection.
What’s next?
Now that your Postgress is set up, you can:- Configure user permissions, schema refreshes, environments and timezone settings
- Learn how Omni generates the model associated with the connection