Connect a Database
Choose the source that contains the answer you need. If you already have approved connection details, open its guide below and enter them in Add connection. Otherwise ask the owner for a reporting identity, the relevant tables or views, authentication details and a network path from Datarelix.
A sign-in account for Datarelix is separate from permission to read a database. Each conversation and dashboard uses one connection. Snowflake uses password-only authentication here; check its current account policy before setup.
Supported dialects
| Dialect | Query language | Default scope | Auth modes |
|---|---|---|---|
| Postgres | SQL | public schema | Username & password · Connection string |
| MySQL | SQL | connected database | Username & password · Connection string |
| Azure SQL / Synapse | T-SQL | dbo schema | Username & password · Connection string · Entra OBO · Service principal — secret · Service principal — certificate |
| Databricks | Spark SQL | default schema | Personal Access Token · OAuth M2M · Federated JWT |
| Kusto (Azure Data Explorer) | KQL | configured database | Entra OBO · App + Certificate |
| BigQuery | GoogleSQL | pick a dataset | Service account JSON · OAuth |
| Athena | Trino/Presto SQL | pick a Glue database | IAM access keys · Assume Role |
| Elasticsearch | ES|QL (8.11+) | pick allowed indices | API key · Basic auth |
| Snowflake | SQL | configured schema | Username & password |
| Files & Object Storage (DuckDB) | DuckDB SQL | configured datasets | AWS S3 · Azure Blob/ADLS · Google Cloud Storage · Direct HTTPS |
Common fields
Every connection has these:
- Name — your label for this connection.
- Dialect — pick one of the dialects above.
- Allowed scope — Datarelix only reads structure and runs queries within this scope. The label changes per dialect (schema / database / dataset / index pattern), but the meaning is the same: the configured boundary for discovery and reporting queries; also restrict the source identity’s effective permissions.
Dialect-specific fields appear after you pick a dialect. See each per-dialect guide for details.
After you connect
Datarelix runs discovery: it reads the tables, columns, types and declared keys in the allowed scope. You can then run AI schema analysis, which adds descriptions and suggests relationships, plus primary keys for tables that declare none. AI schema analysis counts against your plan’s monthly allowance, and you can skip it.
Before analysis starts, you can add optional context: what the database contains, which tables matter most, which columns act as business keys. These notes are sent with the schema structure; no row data is included in discovery or AI schema analysis.
Edits you make on the schema page — descriptions, keys and relationships — take precedence over what discovery and AI schema analysis found. They only change how Datarelix interprets questions; they never change your database.
Re-run discovery any time you add columns or tables. Review the descriptions and relationships before relying on them in a question.
Universal troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
Connection refused | Network reachability | Allow Datarelix’s egress IPs in your database firewall. |
Authentication failed | Wrong credentials | Test with the dialect’s native CLI or console first. |
| Empty schema | Wrong scope | Check Allowed scope — see the per-dialect guide for what blank means. |
| AI schema analysis takes too long | A very large schema | Narrow the allowed scope, or skip AI schema analysis and use discovery only. |
For the error messages shown in the app, see Troubleshooting.