MySQL JDBC Driver Download

Download the MySql JDBC driver, copy the JDBC URL into DbSchema, and start designing schemas with ER diagrams — free Community Edition.

About the MySql JDBC driver

A JDBC driver is a Java .jar library that lets applications connect to MySql. DbSchema uses JDBC to reverse engineer schemas, run SQL, and generate documentation. Driver files are usually published by the database vendor or an open-source project.

JDBC URL format

Host, port, database name, and SSL options are passed in a URL starting with jdbc:. Each MySql driver uses its own syntax — see the connection details below.

The MySql JDBC driver

MySQL is the world's most widely deployed open-source relational database, powering everything from WordPress blogs to large-scale e-commerce platforms. It runs on every major OS and is the go-to choice for LAMP and LEMP stack web applications.

The MySQL JDBC URL

• Required File(s): mysql-connector-java-nn-bin.jar
• Java Driver Class: com.mysql.jdbc.Driver
• JDBC URL: jdbc:mysql://HOST[:PORT][/DB]
• Website: MySQL

Download the MySql JDBC Driver

Last updated August 2025 - verified for MySQL 8.4 / Java 21 compatibility.

The driver library files are compressed in a zip archive. Extract it and load the jar file using DbSchema's Driver Manager.

If you cannot connect, or you get issues with the driver, please ask DbSchema Team for help.

Solving Common MySQL Connectivity Issues

Enable Remote Access on MySql Server

Two separate things keep a remote client out: where the server listens, and where a user is allowed to log in from. Both usually have to be changed.

1. Check where the server listens. MySQL's own default for bind_address is *, every interface. Debian and Ubuntu packages override it with bind-address = 127.0.0.1 in /etc/mysql/mysql.conf.d/mysqld.cnf, which accepts loopback connections only. SHOW VARIABLES LIKE 'bind_address'; reports the value in force. Set it to *, or to the specific address clients use, and restart the service.
2. Grant the user access from your host. A MySQL account is a pair of user and host, so bar@'localhost' and bar@'202.54.10.20' are two different accounts. On the server, start the console with mysql -u root -p and grant the client host explicitly:
   GRANT ALL ON foo.* TO bar@'202.54.10.20' IDENTIFIED BY 'PASSWORD';
   Replace the database, the user and the IP address of the machine running DbSchema. SELECT user, host FROM mysql.user; lists the accounts that already exist.
3. Open port 3306 in the server's firewall. The database listens on port 3306 unless it was installed with a different one. A host firewall on the server blocks incoming connections on that port until a rule allows them. The firewall guide has the commands for Windows, ufw, firewalld and iptables.
4. Connect from DbSchema. In the Connection Dialog choose Remote computer or custom port, fill in the server host and the port, then press Test Connection to check that the server answers before you connect.

An Access denied message means the server was reached and the account or the host was wrong. A timeout instead means the traffic never arrived, so the cause is the bind address or the firewall.

• Or reach the server through SSH. When the database port is deliberately closed to the internet, press Setup SSH Tunnel... in the Connection Dialog and connect through a host that is exposed. The database host and port are then the ones seen from the SSH host — often localhost. See the SSH tunnel guide.

MySql Installation Tips

Install MySql from http://www.mysql.com. During installation go for a detailed install, and when you are prompted for the user password check the 'Enable root access from remote machines'.

Enabling this you will be allowed to connect to MySql from another computer. Remember the password you set here, it will be requested when connecting to the database as user root.

DbSchema and MySQL

DbSchema's ER diagram tool is especially useful for MySQL's InnoDB schemas, where foreign key relationships between tables define the data model. Use the Schema Synchronization feature to safely roll out ALTER TABLE statements across dev, staging, and production without breaking foreign key constraints.