Connection Settings
Connection names, credentials, network access, encryption and timeouts for every Credible data source
These settings apply to every connection, whatever the database. Each type's own fields are on its page under Connect Data.
Connection Names
A connection name can contain only letters, numbers and underscores, and must start with a letter or an underscore: sales_db, not sales-db. Models refer to a connection by this name, as in sales_db.table('orders'), so renaming it later means changing the models too.
Credentials
Credible stores connection credentials and never shows them again. When you edit a connection, a password or key box left empty keeps the stored value. To rotate a credential, enter the new one and save. From the command line, use cred update connection.
Give Credible its own database user or service account, with read access to the schemas you plan to model. Write access is only needed if you persist tables back into that database.
Network Access
Credible queries your database over IPv4, so it needs a route to the database. There are three ways to give it one.
IP Allowlist
For a database reachable from the public internet behind an allowlist, firewall or network policy, add Credible's egress addresses to it. The addresses depend on where your organization runs: contact support for yours.
SSH Bastion (PostgreSQL)
For a PostgreSQL database with no public route, turn on Connect through an SSH bastion in the connection form, and Credible reaches the database through your bastion host. You set this up yourself. See PostgreSQL.
Private NetworkingEnterprise
PrivateLink, VPC connectivity and other private networking are available on the Enterprise plan and enabled on request, for any database type. Contact support to set them up.
Encryption
| Type | How the connection is encrypted |
|---|---|
| PostgreSQL | Set by Database TLS. See PostgreSQL |
| SQL Server | Set by Database TLS. See SQL Server |
| Trino | Use an https:// server URL. An http:// URL is not encrypted |
| BigQuery, Snowflake, Databricks, MotherDuck | Always encrypted by the provider's own client |
| MySQL | The form has no TLS setting |
Timeouts and Cost Limits
| Type | Setting | What it does |
|---|---|---|
| PostgreSQL | Statement timeout (ms) | The database cancels any query that runs longer |
| BigQuery | Query Timeout (ms) | Credible stops waiting for a query after this long |
| BigQuery | Maximum Bytes Billed | BigQuery refuses a query that would bill more than this |
| Snowflake | Response Timeout (ms) | Credible stops waiting for a response after this long |
Leave a field empty to use the database's own limit.