Appearance
Supported Databases (Data Sources)
About 391 wordsAbout 1 min
2026-09-01
Open Data › Datasource, select the Database sources tab, and pick a connector under Choose a database type. The connectors are:
- Apache Doris
- Amazon Redshift
- Azure SQL
- Azure Synapse
- ClickHouse
- Cloudera Impala
- DuckDB
- GaussDB
- GaussDB 200
- Google BigQuery
- Greenplum
- Hive 2
- Impala
- InfluxDB
- MongoDB
- MySQL
- Oracle
- PostgreSQL
- SAP HANA
- Snowflake
- Spark SQL
- SQL Server (Native)
- TiDB
- Transwarp Inceptor
- Vertica
- Generic Database
The Community edition offers only MySQL, PostgreSQL, Oracle and SQL Server (Native).
CSV and Excel files are uploaded as a File Dataset, not as a database connection.
Every connection needs a JDBC driver: choose it in the Driver list of the connection form. If the list has no driver for your database, an administrator uploads one first; see JDBC Driver Management. For a step-by-step example, see Configuring a MySQL Data Source.
Generic Database
Use Generic Database for a database that has a JDBC driver but no connector of its own. Instead of host, port and database name, enter:
| Field | Value |
|---|---|
| Connection name | Name shown in Datafor. |
| Driver | The uploaded JDBC driver JAR for that database. |
| Connection URL | The full JDBC URL from the driver's documentation, for example jdbc:vendor://your-server:port/database. |
| Driver class name | The driver's main class, as given in its documentation. |
| Username / Password | The database account. |
Datafor uses a generic SQL dialect for this connection, so database-specific functions may not be available. Test the reports you need before relying on it.
Who can create a connection
Users with the Create content capability can create connections to database servers. Since 10.00, only administrators can create:
- connections to engines that run inside Datafor, such as DuckDB;
- JNDI connections and connections whose target Datafor cannot identify;
- connections to the database server that holds the Datafor repository.
Ordinary users with Read can still use most of these connections once an administrator has created them (JNDI connections excepted), but custom SQL on sensitive connections is restricted. See Data connections: targets and custom SQL.