Loading page
About this tool
Generate correct JDBC connection URLs for PostgreSQL, MySQL, Oracle, SQL Server, H2 and SQLite with driver-specific syntax.
The JDBC URL Builder assembles a valid JDBC connection string for PostgreSQL, MySQL, Oracle, SQL Server, H2 and SQLite, applying each driver's own grammar rather than one generic template. That matters because the grammars genuinely differ: PostgreSQL and MySQL take `?key=value&key=value`, SQL Server and H2 take `;key=value;`, and the Oracle thin driver takes no URL parameters at all. It returns the URL plus the driver class name, the Maven and Gradle coordinate and a DriverManager snippet, so Java and Kotlin developers can paste a working connection instead of debugging a malformed one.
Open JDBC URL Builder on AltFTool — it loads instantly in your browser.
Paste your code or data sample into the workspace.
Pick the format, conversion, or analysis you need.
Copy the polished result straight back into your project.
Query style for PostgreSQL, MySQL and SQLite; semicolons for SQL Server and H2; none for the Oracle thin driver.
Each URL comes with its class name — com.mysql.cj.jdbc.Driver, not the deprecated com.mysql.jdbc.Driver — and the matching Maven and Gradle dependency.
Warns about relative SQLite and H2 file paths, in-memory H2 vanishing without DB_CLOSE_DELAY=-1, and passwords leaking into logs via the URL.
`jdbc:postgresql://host:port/database`, with the default port 5432 and parameters appended as `?sslmode=require&ApplicationName=billing`. The driver class is org.postgresql.Driver and the dependency is org.postgresql:postgresql. The port can be omitted entirely (`jdbc:postgresql://host/database`) and the driver falls back to 5432.
The service form is `jdbc:oracle:thin:@//host:1521/service_name` and the legacy SID form is `jdbc:oracle:thin:@host:1521:SID` — note the double slash and forward slash in one, colons in the other. Use the service name: from Oracle 12c onward a pluggable database is reached by service, and a SID can stop resolving after a consolidation or move. Neither form accepts query parameters; set connection properties on a java.util.Properties object instead.
Because the Microsoft driver changed its default: since mssql-jdbc 10.2, `encrypt` defaults to true, so a server without a trusted certificate now fails where older driver versions connected happily. The fix is either a properly trusted certificate, or `;encrypt=true;trustServerCertificate=true` for a development server — and remember the whole SQL Server URL is semicolon-separated, including `databaseName=`.
For H2 use `jdbc:h2:mem:testdb`, adding `;DB_CLOSE_DELAY=-1` if the data must survive between connections — otherwise H2 drops the database when the last connection closes. For SQLite use `jdbc:sqlite::memory:` with the org.xerial:sqlite-jdbc driver. Neither takes a host, port or password, since both run inside the JVM process rather than over a socket.