Apache Derby ODBC Driver

⚡ Key Benefits

• Pass-through SQL — Queries are relayed directly to the Derby JDBC driver without SQL rewriting
• Low-code DSN setup — Configure JDBC URL, Derby driver class, JAR file, credentials, and connection parameters in one wizard
• Built-in validation — Use Test Connection and preview query steps before wiring client tools
• Service-ready deployment — Use User DSN for interactive sessions and System DSN for Windows service workloads
• Centralized access option — Publish once through Data Gateway for shared remote access and central control

📸 Visual Overview & Setup

1. Choose JDBC Bridge Driver Type 🔍 View Full Size	2. Enter Full Path for *.jar file (i.e. JDBC driver file) 🔍 View Full Size	3. Preview SQL Query 🔍 View Full Size
4. Load Apache Derby Rows into Excel 🔍 View Full Size	5. Connect from Power BI 🔍 View Full Size	6. Share via Data Gateway Data Gateway overview

🔗 Seamless SQL Query Integration

-- SQL preview from Apache Derby JDBC Bridge setup
SELECT *
FROM "APP"."ORDERS"

🔧 Key Features

Read & Query

• Run Derby SQL from any ODBC client after DSN configuration
• Use the DSN preview area and Select Table dropdown for quick validation
• Follow JDBC SQL examples linked from the same setup guide for advanced patterns

JDBC Bridge Configuration

• Set connection string such as jdbc:derby://hostname:1527/mydatabase for client/server mode
• Set driver class org.apache.derby.jdbc.ClientDriver (or org.apache.derby.jdbc.EmbeddedDriver for embedded mode)
• Provide JDBC file path (for example D:\Apache\derby\lib\derbyclient.jar) and keep extra properties in Connection parameters (e.g., [])
• Use Test Connection before connecting Power BI, Excel, SQL Server, or services

Writes, Limits, and Reliability

• The JDBC Bridge forwards SQL unchanged; INSERT/UPDATE/DELETE support depends on the underlying JDBC driver
• For shared server access, copy DSN settings to Data Gateway, apply firewall rules, and restart the gateway service after updates
• Use guide-provided troubleshooters for Java not found, SSL/cert issues, multi-JAR classpath setup, logging, and local host connection errors

💡 Common Use Cases

Typical scenarios for the Apache Derby ODBC Driver:

• Desktop analytics over Derby: Connect Excel and Power BI to Derby using one reusable DSN.
  Example: validate table output with SELECT * FROM "APP"."ORDERS".
• Service-based integration jobs: Run scheduled data pulls with a System DSN under Windows services.
  Example: nightly sync into SQL Server staging tables.
• Client/server or embedded Derby: Switch JDBC URL and driver class based on Derby deployment mode.
  Example: jdbc:derby:c:\apache\derby\databases\mydatabase for embedded setups.
• Centralized access via gateway: Host the connection once and serve multiple users securely through Data Gateway.
  Example: remote apps connect through ODBC Driver for SQL Server to the gateway host.

🎯 Summary

Bring Apache Derby into the ODBC tools your team already uses.
Configure JDBC Bridge once, validate with Test Connection and query preview, then reuse the DSN across BI tools, SQL Server integrations, and centralized gateway deployments.

Trusted by Developers & IT Teams Worldwide Built for ODBC Workloads — One driver model across BI, ETL, databases, and custom code. Expert Technical Support — Engineers help with JDBC URLs, Java installs, and gateway networking. Proven Enterprise Scale — Thousands of teams worldwide rely on ZappySys for API and cloud connectivity.

ODBC PowerPack Includes Apache Derby ODBC Driver Read reviews on Capterra →