DbSchema supports 70+ SQL and NoSQL databases via JDBC (Java Database Connectivity).
When you create a connection, DbSchema automatically downloads the required JDBC driver.
If downloads are blocked in your environment, click Upload JDBC driver to add the driver .jar file manually.
Looking for your database engine? See the full list →
When starting a new project and selecting Connect to Database, DbSchema first asks you to choose your database type.
Select your database from the list. DbSchema will open the Connection Dialog pre-configured for that database type.
Use the Connection Dialog to configure every aspect of your database connection.
Fill in the following fields:
Connection Name (Alias) — Give the connection a clear name (e.g., Prod-Postgres) to identify it in the Connection Manager.
JDBC Driver — DbSchema automatically downloads the required driver from its public Maven repository. If downloads are blocked, click Upload JDBC driver and supply the .jar file manually. See the JDBC Driver Manager for details.
JDBC URL / Connection Mode — Two modes are available:
Server Location — Choose between:
Test Connection — Click Check (Ping) to verify the server is reachable before proceeding.
Credentials — Enter the database User and Password, then select the target Database.
Optional tabs — Configure SSL/TLS, SSH Tunnel, or Proxy as needed.
Click Connect to establish the connection. The connection is saved for future reuse.
The Connection Manager shows all saved connections. Open it from Connections → Connection Manager.
From here you can create new connections, edit existing ones, duplicate them, or delete them. Double-click a connection to open it.
To connect to a database through an SSH tunnel, open the SSH Tunnel tab in the Connection Dialog and fill in:
The SSH tunnel encrypts the communication between DbSchema and the database server, which is useful when the database port is not exposed directly to the internet. Set the database host and port fields to the address as seen from the SSH host (often localhost if the database runs on the same machine as the SSH server).
Before connecting, you can verify the server is reachable from your machine using standard command-line tools:
ping dbserver.mycompany.comtelnet dbserver.mycompany.com 5432openssl s_client -connect dbserver.mycompany.com:5432If the port is unreachable, check the firewall rules on the database server. See the Firewall guide for instructions.
The Options tab provides additional settings for the connection: