Workspace

Connections

Connections are the starting point for most Dory workflows. A connection defines how Dory reaches a database and what credentials it uses.

What You Can Manage

  • Database type.
  • Host, port, database, username, and password.
  • SSL, SSH Tunnel, and deployment-specific options.
  • Local database file paths for SQLite or DuckDB.
  • Workspace-level organization and naming.

Supported Connection Types

TypeTypical Use
ClickHouseAnalytics, events, monitoring, and operational data
PostgreSQL / NeonProduct and application databases
MySQL / MariaDBBusiness systems and web applications
SQL ServerEnterprise applications, reporting, and operational systems
OracleERP, finance, enterprise systems, and long-running production data
SQLiteLocal files, demos, and small datasets
DuckDB / MotherDuckLocal analytics and file-based analysis

Create a Connection

  1. Open your workspace.
  2. Choose Add Connection.
  3. Select the database type.
  4. Fill in required settings.
  5. Test the connection.
  6. Open Explorer to confirm schema visibility.

Desktop SQLite File Flow

In the Dory desktop app, local SQLite files can be used directly as database connections. This is the common flow for demos, local datasets, and small file-based analysis:

  1. Open the Dory desktop app.
  2. Go to Connections and choose Add Connection.
  3. Select SQLite as the connection type.
  4. Enter an absolute database file path, such as /Users/Shared/Data/demo.sqlite.
  5. Create the connection.
  6. Select the new connection before moving to SQL Console.

For SQLite, importing the file means pointing Dory at the local .sqlite or .db file path. The file remains on your machine, and the desktop runtime reads it through that path.

Dory desktop SQLite connection

Connection Checklist

  • Use credentials with the least privileges needed.
  • Confirm network access from the Dory runtime.
  • Use SSL when required by the database provider.
  • Use absolute paths for local database files.
  • In Docker, mount local file paths into the container.

Naming Recommendations

Use names that make environment and ownership clear, such as:

  • prod-clickhouse-events
  • staging-postgres-app
  • local-sqlite-demo
  • analytics-duckdb-reports

How is this guide?