Download EnterpriseDB JDBC Driver

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

About the EnterpriseDB JDBC driver

A JDBC driver is a Java .jar library that lets applications connect to EnterpriseDB. 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 EnterpriseDB driver uses its own syntax — see the connection details below.

The EnterpriseDB JDBC driver

EnterpriseDB (EDB) Postgres Advanced Server is an enterprise-grade distribution of PostgreSQL with added Oracle compatibility features, security enhancements, and performance optimizations. It includes Oracle-compatible PL/SQL procedures, packages, and built-in functions, enabling migration of Oracle workloads to an open-source foundation. EDB is widely used in regulated industries requiring enterprise support and compliance certifications.

The EnterpriseDB (EDB) JDBC URL

• Required File(s): postgresql-xxx.jar (PostgreSQL JDBC Driver)
• Java Driver Class: org.postgresql.Driver
• JDBC URL: jdbc:postgresql://{HOST}:{PORT}/{DB}
• Website: EnterpriseDB (EDB)

EDB Postgres Advanced Server uses port 5444 by default, unlike standard PostgreSQL's port 5432. The standard PostgreSQL JDBC driver is fully compatible with EDB. EDB-specific features such as Oracle-compatibility packages and advanced partitioning are accessible via the standard PostgreSQL wire protocol.

Connecting to a Remote EDB Server

EDB Postgres Advanced Server is configured like PostgreSQL, with one difference that causes most of the failed connections: the port.

1. Use port 5444, not 5432. The EDB installer listens on 5444 by default — or the first free port after it, if 5444 was taken when the server was installed. The PGPORT variable set by the pgplus_env script tells you the real value, and so does SHOW port;.
2. Let the server listen on the network. Set listen_addresses = '*' in postgresql.conf and restart the service; the default localhost accepts loopback connections only. SHOW config_file; locates the file.
3. Allow your user to log in from your host. Add a record such as host all all 192.168.1.0/24 scram-sha-256 to pg_hba.conf and run SELECT pg_reload_conf();.
4. Open port 5444 in the server's firewall. The database listens on port 5444 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.
5. 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.

The community PostgreSQL JDBC driver connects to EDB without any change — the Oracle-compatibility layer is server-side, so packages, procedures and EDB's partitioning all arrive over the normal PostgreSQL wire protocol.

DbSchema and EnterpriseDB (EDB)

DbSchema connects to EnterpriseDB Postgres Advanced Server using the standard PostgreSQL JDBC driver, rendering EDB-specific schema elements including Oracle-compatibility packages, procedures, and advanced partitioning structures through the visual schema designer.