To add a database connection, click on the gear icon in the top right, and navigate to Admin settings > Databases > Add a database.
Fill out the fields for that database, and click Save changes at the bottom.
You can edit these settings at any time. Just remember to save your changes.
The display name for the database in the Metabase interface.
Your database’s IP address, or its domain name (e.g., esc.mydatabase.com).
The database port. E.g., 8080.
Presto catalogs contain schemas and reference data sources via a connector.
Only add tables to Metabase that come from a specific schema.
The database username for the account that you want to use to connect to your database. You can set up multiple connections to the same database using different user accounts to connect to the same database, each with different sets of privileges.
The password for the username that you use to connect to the database.
Use a secure connection (SSL)
Metabase automatically tries to connect to databases with SSL first, then without if that doesn’t work. If it’s possible to connect to your database with an SSL connection, Metabase will make that the default setting for your database. If you prefer to connect without this layer of security, you can always change this setting later, but we highly recommend keeping SSL turned on to keep your data secure.
Use SSL certificate?
Metabase supports both keystores and truststores.
You can specify a local file path, or upload a keystore. You’ll also need to input your keystore password.
You can specify a local file path, or upload a truststore. You’ll also need to input your truststore password.
s### Authenticate with Kerberos
Kerberos settings include:
- Kerberos principal (e.g.,
- Kerberos coordinator service (e.g.,
- You can use a canonical hostname.
- Kerberos credential cache file (e.g.,
- Kerberos keytab file (e.g.,
- Kerberos configuration file (e.g.,
- Presto coordinator Kerberos service principal pattern (e.g.,
Additional JDBC connection string options
You can append options to the connection string that Metabase uses to connect to your database.
Re-run queries for simple explorations
Turn this option OFF if people want to click Run (the play button) before applying any Summarize or filter selections.
By default, Metabase will execute a query as soon as you choose an grouping option from the Summarize menu or a filter condition from the action menu. If your database is slow, you may want to disable re-running to avoid loading data on each click.
Choose when Metabase syncs and scans
Turn this option ON to manage the queries that Metabase uses to stay up to date with your database. For more information, see Syncing and scanning databases.
If you’ve selected Choose when syncs and scans happen > ON, you’ll see the following options under Database syncing:
- Scan sets the frequency of the sync query to hourly (default) or daily.
- at sets the time when your sync query will run against your database (in the timezone of the server where your Metabase app is running).
Scanning for filter values
Metabase can scan the values present in each field in this database to enable checkbox filters in dashboards and questions. This can be a somewhat resource-intensive process, particularly if you have a very large database.
If you’ve selected Choose when syncs and scans happen > ON, you’ll see the following options under Scanning for filter values:
- Regularly, on a schedule allows you to run scan queries at a frequency that matches the rate of change to your database. The time is set in the timezone of the server where your Metabase app is running. This is the best option for a small database, or tables with distinct values that get updated often.
- Only when adding a new filter widget is a great option if you want scan queries to run on demand. Turning this option ON means that Metabase will only scan and cache the values of the field(s) that are used when a new filter is added to a dashboard or SQL question.
- Never, I’ll do this manually if I need to is an option for databases that are either prohibitively large, or which never really have new values added. Use the Re-scan field values now button to run a manual scan and bring your filter values up to date.
Periodically refingerprint tables
Turn this option ON to scan a sample of values every time Metabase runs a sync.
A fingerprinting query examines the first 10,000 rows from each column and uses that data to guesstimate how many unique values each column has, what the minimum and maximum values are for numeric and timestamp columns, and so on. If you turn this option OFF, Metabase will only fingerprint your columns once during setup.
Default result cache duration
Database-specific caching is only available on Pro and Enterprise plans (both self-hosted and on Metabase Cloud).
How long to keep question results. By default, Metabase will use the value you supply on the cache settings page, but if this database has other factors that influence the freshness of data, it could make sense to set a custom duration. You can also choose custom durations on individual questions or dashboards to help improve performance.
- Use instance default (TTL). TTL is time to live, meaning how long the cache remains valid before Metabase should run the query again.
If you are on a paid plan, you can also set cache duration per questions. See Advanced caching controls.