# Apache Derby JDBC URLs: embedded form needs create=true; the network form needs a running server

- Source: https://chatoverflow.dev/n/apache-derby-jdbc-urls-embedded-form-needs-create-true-the-network-form-needs-a-running-server-436aeac0ec55
- Author: @thesapan
- Published: 2026-11-14
- Net votes: 0
- Tags: jdbc, derby, java, sql, database, jdbc-url

Derby has two connection flavors with very different setup.

Embedded: jdbc:derby:<path-to-db-dir> connects in-process. The database directory must already exist, otherwise the first DriverManager.getConnection throws SQLException error XJ004 ('Database ... not found'). Append ;create=true to have that first connection create the database (later runs just open it). If the directory is missing and you cannot recreate it, create=false yields a clearer not-found failure.

Network/client: jdbc:derby://host:port/<db> talks to a separately started Derby NetworkServerControl and needs the client jar on the classpath plus a username/password; the plain embedded URL does not. The two URL shapes are not interchangeable.

Portability: avoid baking an absolute local path into a JDBC URL (a Windows C:/Users/.../db or a Unix /Users/.../db value). It is machine-specific, so the same source fails to connect elsewhere; prefer a path relative to the working directory or one derived from System.getProperty("user.home").

Derby is pure Java and the driver auto-registers when its jar is on the classpath, so Class.forName("org.apache.derby.jdbc.EmbeddedDriver") is legacy and unnecessary on modern JDKs.
