The Neo4J ADO.NET Data Provider enables user to easily connect to Neo4J data from .NET applications. Rapidly create and deploy powerful .NET applications that integrate with Neo4J.
Neo4J .NET Connectivity Features
- Fully compatible with Neo4j versions 4.2 and above
- Connect to live Neo4J data, for real-time data access with the Neo4J ODBC Driver
- Full support for data aggregation and complex JOINs in SQL queries
- Secure connectivity through modern cryptography, including TLS 1.2, SHA-256, ECC, etc.
- Seamless integration with leading BI, reporting, and ETL tools and with custom applications via the Neo4J Connector.
Target Service, API
The driver connects to Neo4j graph database. Property graph database.
Schema, Data Model
Models Neo4j nodes and relationships as tables. Graph data in relational form.
Key Objects
Nodes, Relationships, and Properties. Graph database access via SQL.
Operations
Cypher queries through SQL interface. Pattern matching. Graph algorithms.
Authentication
Neo4j authentication. Bolt protocol connection. SSL support.
See what you can do with Neo4J ADO.NET provider
Use Neo4J from SQL Server Analysis Service (SSAS) multi-dimensional cubes. Keep your analytical data modeling and access to any source including cloud and on-premises.
The Neo4J ADO.NET Provider allows developers to build applications that connect to Neo4J using familiar SQL and Entity Framework. Integrate Neo4J to your mission -critical applications or create easy side-by-side applications.
You can connect from ADO.NET compliant low-code development tools:
You can connect Neo4J from .NET-based reporting and analytics tools:
Standard ADO.NET Access to Neo4J
The Neo4J ADO.NET Provider offers the most natural way to access Neo4J data from any .NET application. Simply use Neo4J Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the Neo4J Data Provider through Visual Studio Server Explorer, in code through familiar classes, and in data controls like DataGridView, GridView, DataSet, etc.
The CData ADO.NET Provider for Neo4J hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
Working with DataAdapters, DataSets, DataTables, etc.
The Neo4J Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: Neo4JConnection, Neo4JCommand, Neo4JDataAdapter, Neo4JDataReader, Neo4JDataSource, Neo4JParameter, etc. Because of this you can now access Neo4J data in an easy, familiar way.
For example:
using (Neo4JConnection conn = new Neo4JConnection("...")) {
string select = "SELECT * FROM Neo4J";
Neo4JCommand cmd = new Neo4JCommand(select, conn);
Neo4JDataAdapter adapter = new Neo4JDataAdapter(cmd);
using (adapter) {
DataTable table = new DataTable();
adapter.Fill(table);
...
}
}
ADO.NET Provider Performance
With traditional approaches to remote access, performance bottlenecks can spell disaster for applications. Regardless if an application is created for internal use, a commercial project, web, or mobile application, slow performance can rapidly lead to project failure. Accessing data from any remote source has the potential to create these problems. Common issues include:
- Network Connections - Slow network connections and latency issues are common in mobile applications.
- Service Delays - Delays due to service interruptions, resulting in server hardware or software updates.
- Large Data - Intentional or unintentional requests for large amounts of data.
- Disconnects - Complete loss of network connectivity.
The CData ADO.NET Provider for Neo4J solves these issues by supporting powerful smart caching technology that can greatly improve the performance and dramatically reduce application bottlenecks.
Smart Caching
Smart caching is a configurable option that works by storing queried data into a local database. Enabling smart caching creates a persistent local cache database that contains a replica of data retrieved from the remote source. The cache database is small, lightweight, blazing-fast, and it can be shared by multiple connections as persistent storage.
Caching with our ADO.NET Providers is highly configurable, including options for:
- Auto Cache - Maintain an automatic local cache of data on all requests. The provider will automatically load data into the cache database each time you execute a SELECT query. Each row returned by the query will be inserted or updated as necessary into the corresponding table in the cache database.
- Explicit Cache - Cache only on demand. Developers decide exactly what data gets stored in the cache and when it is updated. Explicit caching provides full control over the cache contents by using explicit execution of CACHE statements.
- No Cache - All requests access only live data and no local cache file is created.
This powerful caching functionality increases application performance and allows applications to disconnect and continue limited functioning without writing code for additional local storage and/or data serialization/deserialization.
More information about ADO.NET Provider caching and best caching practices is available in the included help files.
Visual Studio Integration & Server Explorer
Working with the new Neo4J ADO.NET Provider is easy. As a fully-managed .NET Data Provider, the Neo4J Data Provider integrates seamlessly with the Visual Studio development environment as well as any .NET application.
As an ADO.NET Data Provider, Neo4J ADO.NET Provider can be used to access and explore Neo4J data directly from the Visual Studio Server Explorer.
It's easy. As a standard ADO.NET adapter, developers can connect the Server Explorer to Neo4J ADO.NET Provider just like connecting to any standard database.
- Add a new Data Connection from the Server Explorer and select the Neo4J Data Source
- Configure the basic connection properties to access your Neo4J account data.
Explore all of the data available! Neo4J ADO.NET Provider makes it easy to access live Neo4J data from Visual Studio.
- After configuring the connection, explore the feeds, views, and services provided by the Neo4J Data Source.
- These constructs return live Neo4J data that developers can work with directly from within Visual Studio!
Developer Integration: Databind to Neo4J
Connecting Web, Desktop, and Mobile .NET applications with Neo4J is just like working with SQL Server. It is even possible to integrate Neo4J ADO.NET Provider into applications without writing code.
Developers are free to access the Neo4J ADO.NET Provider in whatever way they like best. Either visually through the Visual Studio Winforms or Webforms designers, or directly through code.
- Developers can connect the Neo4J Data Source directly to form components by configuring the object's smart
tags.
- Add a new Data Connection from the Server Explorer and select the Neo4J Data Source. Then, select the
feed, view, or services you would like to connect the object to.
Done! It's just like connecting to SQL Server.
- Once the object is bound to the data source, applications can easily interact with Neo4J data with full
read/write (CRUD) support.
Popular ADO Videos:
