Connect & Ingest data from / to a MotherDuck database

Sling CLI Setup

The following credentials keys are accepted:

  • database (required) -> The motherduck database name

  • motherduck_token (required) -> The service token. See here for instructions on getting it.

  • schema (optional) -> The default schema to use.

  • duckdb_version (optional) -> The CLI version of DuckDB to use. You can also specify the env. variable DUCKDB_VERSION.

  • read_only (optional) -> Whether to open the connection in readonly mode. Accepts true or false. Default is false.

  • interactive (optional) -> Whether to communicate to the DuckDB CLI via interactive mode instead of reopening the connection each time. Accepts true or false. Default is true.

Here are examples of setting a connection named MOTHERDUCK. We must provide the type=motherduck property:

$ sling conns set MOTHERDUCK type=motherduck database=my_db motherduck_token=xxxxxxxxxxxx

# Or use url
$ sling conns set MOTHERDUCK url="motherduck://my_db?motherduck_token=xxxxxxxxxxxx"

Environment Variable

export MOTHERDUCK='motherduck://my_db?motherduck_token=xxxxxxxxxxxx'

Sling Env File YAML

See here to learn more about the sling env.yaml file.

    type: motherduck
    database: <database>
    motherduck_token: <motherduck_token>
    schema: <schema>
    duckdb_version: '<duckdb_version>'

Specifying a DuckDB version

If you would like to use a specific DuckDB version, you can specify this way:

export DUCKDB_VERSION='0.7.0'

If you are facing issues connecting, please reach out to us at, on discord or open a Github Issue here.

Potential Issue

If you have a .duckdbrc file, which runs commands whenever the DuckDB CLI is invoked, this may interfere with normal Sling operation. If you are facing weird issues and have this file, try again after deleting it.

Last updated