Skip to main content
In this guide, you’ll learn how to connect your MotherDuck database to Omni.

​
Requirements

To follow the steps in this guide, you’ll need:
  • Organization Admin permissions in Omni
  • A MotherDuck database using MotherDuck v0.10.2 or higher

​
Setup

1

Create a MotherDuck access token

  1. Sign in to your MotherDuck account.
  2. In top left corner of the page, click the organization name and then Settings.
  3. Click Integrations > Access Tokens.
  4. Click + Create token.
  5. Enter a Name for the token to make it easy to recognize. For example: Omni connection
  6. For Token type, select Read/Write token.
  7. Optional. Define expiration settings for the token.
  8. Click Create token.
  9. Copy the token. Note: The token will only display once, so make sure you copy it before closing the dialog.
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 CSV uploads in joins.
In this step, create a dedicated schema to use for table uploads. This can be in its own database or the same database as other schemas to be used in modeling. Note: The upload schema can’t be used for other modeled tables.
3

Create the connection in Omni

  1. In Omni, click Settings > Connections.
  2. Click the Motherduck option.
  3. On the connection setup page, fill in the connection details:
    NameRequired?Description
    Display Name YesA user-friendly name for the connection, which will be used throughout Omni
    Database YesThe database to connect to
    Include Other Catalogs NoA comma-separated list of other catalogs to include
    Include Schemas NoA comma-separated list of schemas to include in the connection
    Offloaded Schemas NoA 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 NoThe 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.
    Token YesThe MotherDuck authentication token you created in step 1
    Database Timezone YesThe timezone used by the database
    Query Timezone YesThe 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 NoAllow users to override the connection timezone with their own when querying
  4. When finished, click Create connection.

​
What’s next?

Now that your MotherDuck is set up, you can: