Requirements
To follow the steps in this guide, you’ll need:- Organization Admin permissions in Omni
- Permissions in Redshift that allow you to create database users and grant permissions
Setup
1
Create a database user for Omni
In your Redshift database, run the following command to create a database user for Omni:Next, run the following command for each schema you want to use in Omni:
Create an Omni database user
Grant Omni access to schemas
2
Set up a table upload schema
This step is optional. However, we recommend completing it as part of the initial set up or you won’t be able to use uploaded files like CSVs in joins.
- Create the schema in Redshift.
-
Run the following to grant the Omni user the required privileges:
Grant Omni access to table upload schema
3
Allowlist Omni's IP addresses
If access to the Redshift database is limited by IP address, you’ll need to add Omni’s IPs to the allowlist before you create the database connection. For Redshift, this typically means creating a security group and adding an inbound traffic rule for each IP address.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 Redshift 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 5439. 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. Default Schema No The default schema to use for queries. Defaults to public.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 - When finished, click Create connection.
What’s next?
Now that your database is set up, you can:- Configure user permissions, schema refreshes, environments and timezone settings
- Learn how Omni generates the model associated with the connection