Configure the list of available databases

When configuring your Datalore On-Premises instance, you can customize the list of database connectors available to users. This allows you to enforce your organization’s environment-specific requirements or security policies to align with your environment requirements or security policies.

By modifying the list, you control what connectors are visible in the UI and what database connections users are allowed to configure using connection strings.

Allow databases

To allow only specific database types to be available when creating a connection, list the corresponding database IDs in the configuration file.

In docker-compose.yaml, add the IDs from the supported database list as a comma-separated list to environment.DATABASES_FILTER_INCLUDE as in the following example:

environment:
  ...
  DATABASES_FILTER_INCLUDE: "postgresql, clickhouse, mariadb"
        

In datalore.values.yaml, add the IDs from the supported database list as a comma-separated list to dataloreEnv.DATABASES_FILTER_INCLUDE as in the following example:

dataloreEnv:
  ...
  DATABASES_FILTER_INCLUDE: "postgresql, clickhouse, mariadb"
        

If the list is empty, all default database types will be available.

Hide databases

To hide specific database types when creating a connection, list the corresponding database IDs in the configuration file.

In docker-compose.yaml, add the IDs from the supported database list as a comma-separated list to environment.DATABASES_FILTER_EXCLUDE as in the following example:

environment:
  ...
  DATABASES_FILTER_EXCLUDE: "elasticsearch, oracle"
        

In datalore.values.yaml, add the IDs from the supported database list as a comma-separated list to dataloreEnv.DATABASES_FILTER_EXCLUDE as in the following example:

dataloreEnv:
  ...
  DATABASES_FILTER_EXCLUDE: "elasticsearch, oracle"
        

If the list is empty, all default database types will be available.

Supported databases

Database name	Database ID
Athena	`athena`
Google Cloud Spanner	`cloudspanner`
Elasticsearch	`elasticsearch`
Firebird	`firebird`
SAP Hana	`hana`
Informix	`informix`
InterSystems IRIS	`intersystemsiris`
OpenEdge	`openedge`
Apache Phoenix	`phoenix.thick`
Apache Phoenix Thin	`phoenix.thin`
Presto	`presto`
Tarantool	`tarantool`
Teradata	`teradata`
Tibero	`tibero`
Trino	`trino`
Mimer SQL	`mimiersql`
Apache Ignite	`ignite`
Google BigQuery	`bigquery`
ClickHouse	`clickhouse`
IBM Db2	`db2.11`
IBM Db2 for 9.X, 10.X	`db2`
IBM Db2 (JTOpen)	`db2.jtopen`
Apache Derby (Remote)	`derby.remote`
Exasol	`exasol`
H2	`h2.unified`
Apache Hive	`hive`
MariaDB	`mariadb`
Microsoft SQL Server	`sqlserver.ms`
Microsoft SQL Server (jTds)	`sqlserver.jtds`
Azure SQL Database	`azure.ms`
Microsoft SQL Server LocalDB	`sqlserver.localdb.jtds`
Azure Synapse Analytics	`synapse.ms`
MySQL	`mysql.8`
SingleStore	`memsql`
TiDB	`tidb`
Amazon Aurora MySQL	`mysql_aurora`
Oracle	`oracle.19`
Oracle for 9.X, 10.X, 11.1	`oracle`
PostgreSQL	`postgresql`
YugabyteDB	`yugabyte`
CockroachDB	`cockroach`
Greenplum	`greenplum`
Amazon Redshift	`redshift`
Snowflake	`snowflake`
Apache Spark	`spark`
Sybase (jTds)	`sybase.jtds`
Sybase	`sybase.ase`
Vertica	`vertica`

29 May 2026