DbSchema supports connections to various SQL and some NoSQL databases. A proper JDBC Driver is required for this connection. When you connect to a database, DbSchema automatically retrieves the necessary JDBC driver from its public web repository.
To learn how to configure the connection dialog, click here. If your database is hosted on a different computer, you will need to provide the correct TCP/IP HostName. For certain databases, you may also need to enable remote connections, activate TCP/IP, grant user access, or configure firewall settings. More details can be found in the next section.
If the database you're looking for is missing from the JDBC driver list you can upload the driver in DbSchema.
See all supported databases here.
The connection dialog allows you to configure connections to any database with ease.
C:\Users\<YourUser>\.DbSchema\drivers\SqlServer...
.
DbSchema automatically builds the JDBC URL using the values you provide for host, port, and database fields.
For cloud databases (e.g., AWS, Azure, Google Cloud), choose Edit Manually and copy the URL from the cloud console. A text field will appear for entering the JDBC URL.
You can find the hostname on a Windows server using several methods:
cmd
, and press Enter.hostname
ipconfig
ipconfig /all
nslookup
nslookup <IP address>
<IP address>
with the server's IP. If a reverse DNS entry exists, this will return the hostname.nbtstat
nbtstat -A <IP address>
<IP address>
with the actual IP. This displays the NetBIOS name table, which includes the hostname.Use the terminal to retrieve the hostname:
hostname
cat /proc/sys/kernel/hostname
You can find the hostname of your Mac in the System Preferences:
If you still can't determine the hostname or have trouble connecting, please contact your system administrator or network support team.
ipconfig
ip addr show
— recommended for newer systemsifconfig -a
— for older systems (requires net-tools
)inet
under the active interface (e.g., eth0
, wlan0
).
Note: If your server is behind a router, firewall, or VPN, the displayed address may be an internal IP (e.g., 192.168.x.x
).
To find the external IP address, open a browser on the server and visit whatismyipaddress.com.
Before connecting DbSchema to a remote database server, it's useful to test whether the server is reachable from your machine. Here are three methods to verify connectivity: using ping, telnet, or openssl.
openssl
or telnet
on Windows, you can install the Git client and use Git Bash, or install telnet
from Windows Features.
This checks basic network reachability.
ping <hostname or IP>
Example:
ping dbserver.mycompany.com
ping 192.168.1.25
This tests if a specific port (e.g., the database port) is open and accepting connections.
telnet <hostname or IP> <port>
Example:
telnet dbserver.mycompany.com 5432 # PostgreSQL
telnet 192.168.1.25 3306 # MySQL
Useful for testing encrypted ports such as MySQL over SSL, PostgreSQL with SSL, etc.
openssl s_client -connect <hostname or IP>:<port>
Example:
openssl s_client -connect dbserver.mycompany.com:5432
These tools help verify if the database server is reachable and listening on the correct port. If you're still unable to connect, check firewalls, database server status, and network settings.
Establish an SSH Tunnel to encrypt the communication to the database.
In the Options section you can modify details about your model.
Windows Firewall is blocking connectivity from other machines. To allow connectivity you have to create a new Inbound rule for the database port. Go to Control Panel > System and Security > Windows Defender Firewall > Advanced Settings > Inbound Rules and follow the “New Rule” wizard.