Connect to Neo4j through standard ODBC by configuring the ZappySys JDBC Bridge Driver without Java coding.

Download the neo4j-jdbc-full-bundle JAR, create a DSN with a jdbc:neo4j URL (add enableSQLTranslation=true for SQL-style queries), validate with Test Connection, and preview before wiring Excel, Power BI, or ETL jobs.
Part of ZappySys ODBC PowerPack (30+ drivers).

Recommended starting point

View Setup Guide & Get Started →

See features, UI & examples →

Pro Tip: The integration hub requires Java 17 minimum (Java 21 recommended). Download the bundle from MVN Repository and point the DSN at your local JAR (for example E:\Drivers\JDBC\neo4j-jdbc-full-bundle.jar). Append ?enableSQLTranslation=true to use SQL; omit it for Cypher. For TLS and Aura patterns, follow Neo4j JDBC configuration. Use a User DSN for interactive design and a System DSN for Windows services; match ODBC bitness to the host process. For help, search ZappySys Community.

Compatibility: Windows ODBC (32/64-bit) | Works with Visual Studio, .NET, BI tools | Data Gateway for SQL Server, JDBC, and non-Windows access

⚡ Key Benefits

Neo4j over ODBC — Reach graph data through a JDBC Bridge DSN your ODBC tools already understand
SQL or Cypher — Use enableSQLTranslation=true for SQL previews; drop it when you want native Cypher through the same driver
Official JDBC bundle — Reference neo4j-jdbc-full-bundle in the DSN per the setup guide
Validated connectivity — Test Connection plus in-DSN query preview before production workloads
Optional Data Gateway — Centralize Neo4jDSN for shared ODBC access and simpler control

Learn more about Data Gateway

📸 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 Neo4j 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

Example SQL query from the setup guide (requires enableSQLTranslation=true)

SELECT * FROM Movie

✔ SQL translation maps labels such as Movie to graph data
✔ For Cypher, use a URL without enableSQLTranslation (see hub)
✔ Works inside SQL Server, Power BI, Excel

🔧 Key Features

Read & Query

Run SQL against Neo4j when enableSQLTranslation=true is set on the JDBC URL
Switch to Cypher by using jdbc:neo4j://host:7687 without the translation flag, e.g. MATCH (m:Movie) RETURN m.title AS Movie
Use the preview grid or metadata picker when the driver exposes node labels as tables
See more patterns in JDBC Bridge SQL query examples

JDBC Bridge Configuration

Example JDBC URL (non-SSL SQL) from the guide: jdbc:neo4j://neo4j-instance-host-name:7687?enableSQLTranslation=true
TLS SQL example: jdbc:neo4j+s://neo4j-instance-host-name:7687?enableSQLTranslation=true
AuraDB SQL example from the guide: jdbc:neo4j+s://1234abcd.databases.neo4j.io?enableSQLTranslation=true
Example DSN name from the guide: Neo4jDSN
Point JDBC driver file(s) at your local JAR (example path: E:\Drivers\JDBC\neo4j-jdbc-full-bundle.jar)
Example credentials from the guide: user neo4j with your database password
Set Connection parameters to [] when no extra properties are required
Run Test Connection to confirm Java 17+, JAR path, and Bolt reachability on port 7687

Writes & Driver Behavior

The bridge forwards SQL or Cypher unchanged; write support depends on your Neo4j edition, JDBC bundle version, and grants
If you see action is not supported, that reflects the JDBC driver rather than the ZappySys bridge

Reliability & Platform Fit

Standard ODBC 3.x for Power BI, Excel, SQL Server linked servers, SSIS ODBC Source, and custom apps
Prefer Java 21 when your Neo4j JDBC build supports it; the hub documents Java 17 as the minimum
For Data Gateway deployments, copy DSN settings to the gateway host, adjust firewall rules, and restart the gateway service after edits
Use the guide’s Troubleshooters & resources (JDBC Bridge Driver) list for Java discovery, SSL, multi-JAR merges, logging, and disconnect errors
Learn more in ZappySys JDBC Bridge Driver documentation

💡 Common Use Cases

Typical scenarios for the Neo4j ODBC Driver:

Graph analytics in BI: Refresh Excel or Power BI against Neo4j using SQL translation for familiar SELECT syntax.
Example: preview SELECT * FROM Movie in the DSN before publishing dashboards.
ETL and warehousing: Extract graph-backed entities into SQL Server for downstream processing.
Example: scheduled jobs using a System DSN under a service account.
Gateway sharing: Publish Neo4jDSN on Data Gateway for ODBC Driver for SQL Server clients.
Example: teams reuse ZappySysGatewayDSN with default database set to the gateway data source name.
Service automation: Match 32-bit vs 64-bit ODBC Administrator with the host process.
Example: align SQL Agent steps with the correct DSN bitness.

🎯 Summary

Bring Neo4j into ODBC-native tools without hand-rolling JDBC hosts.
Install Java 17+, add the Neo4j JDBC bundle, build a JDBC Bridge DSN with the right URL mode (SQL translation vs Cypher, plain vs neo4j+s), validate connectivity, and reuse the same DSN across Excel, Power BI, SQL Server, and optional Data 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 Neo4j ODBC Driver