Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →
Databricks ADO.NET Provider
SQL-based Access to Databricks through ADO.NET for your custom .NET applications and SSAS.
.NET developers and tools users
ADO.NET Connector
Continue on this page for more detail or get the free trial now
SQL Server Analysis Service (SSAS) users
SSAS + Databricks
Connect Databricks to SSAS OLAP cube
The Databricks ADO.NET Data Provider enables user to easily connect to Databricks from .NET applications. Rapidly create and deploy powerful .NET applications that integrate with Databricks.
Databricks
Databricks Connectivity Features
- SQL access to Databricks lakehouses
- Connect to live Databricks data, for real-time data access
- 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
Target Service, API
The driver supports all versions of Databricks from Runtime Versions 9.1 - 13.X including both Pro and Classic Databricks SQL versions. Compatible with Databricks clusters hosted on any cloud platform (AWS, Azure, GCP).
Schema, Data Model
Models Databricks data as relational tables with dynamic metadata discovery. The driver automatically detects table definitions data types and relationships. Supports Databricks Delta tables and provides access to workspace objects.
Key Objects
Databricks Clusters, Jobs, Workspace files, Notebooks, Delta tables, Views, and Databases. Provides access to both managed and external tables in the Databricks metastore.
Operations
Full CRUD operations with ANSI SQL-92 support. Pushes down filters, aggregations, and other SQL operations directly to Databricks for optimal performance. Supports complex JOINs and handles unsupported operations client-side. Enables batch operations and efficient data processing through Spark SQL integration.
Authentication
Supports Personal Access Token authentication, OAuth 2.0 (M2M and U2M), OAuth token pass-through, Azure Service Principal, and Azure AD authentication. Also supports OAuth 2.0 browser-based authentication for local applications.
See what you can do with Databricks ADO.NET provider
Use Databricks 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 Databricks ADO.NET Provider allows developers to build applications that connect to Databricks using familiar SQL and Entity Framework. Integrate Databricks 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 Databricks from .NET-based reporting and analytics tools:
Standard ADO.NET Access to Databricks
The Databricks ADO.NET Provider offers the most natural way to access Databricks data from any .NET application. Simply use Databricks Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the Databricks 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 Databricks 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 Databricks Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: DatabricksConnection, DatabricksCommand, DatabricksDataAdapter, DatabricksDataReader, DatabricksDataSource, DatabricksParameter, etc. Because of this you can now access Databricks data in an easy, familiar way.
For example:
using (DatabricksConnection conn = new DatabricksConnection("...")) {
string select = "SELECT * FROM Cluster";
DatabricksCommand cmd = new DatabricksCommand(select, conn);
DatabricksDataAdapter adapter = new DatabricksDataAdapter(cmd);
using (adapter) {
DataTable table = new DataTable();
adapter.Fill(table);
...
}
}
More Than Read-Only: Full Update/CRUD Support
Databricks Data Provider goes beyond read-only functionality to deliver full support for Create, Read, Update, and Delete operations (CRUD). Your end-users can interact with the data presented by the Databricks Data Provider as easily as interacting with a database table.
using (DatabricksConnection connection = new DatabricksConnection(connectionString)) {
DatabricksDataAdapter dataAdapter = new DatabricksDataAdapter(
"SELECT Id, Where FROM Cluster", connection);
dataAdapter.UpdateCommand = new DatabricksCommand(
"UPDATE Cluster SET Where = @Where " +
"WHERE Id = @ID", connection);
dataAdapter.UpdateCommand.Parameters.AddWithValue("@Where", "Where");
dataAdapter.UpdateCommand.Parameters.AddWithValue("@Id", "80000173-1387137645");
DataTable ClusterTable = new DataTable();
dataAdapter.Fill(ClusterTable);
DataRow firstrow = ClusterTable.Rows[0];
firstrow["Where"] = "New Location";
dataAdapter.Update(ClusterTable);
}
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 Databricks 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 Databricks ADO.NET Provider is easy. As a fully-managed .NET Data Provider, the Databricks Data Provider integrates seamlessly with the Visual Studio development environment as well as any .NET application.
As an ADO.NET Data Provider, Databricks ADO.NET Provider can be used to access and explore Databricks data directly from the Visual Studio Server Explorer.
It's easy. As a standard ADO.NET adapter, developers can connect the Server Explorer to Databricks ADO.NET Provider just like connecting to any standard database.
- Add a new Data Connection from the Server Explorer and select the Databricks Data Source
- Configure the basic connection properties to access your Databricks account data.
Explore all of the data available! Databricks ADO.NET Provider makes it easy to access live Databricks data from Visual Studio.
- After configuring the connection, explore the feeds, views, and services provided by the Databricks Data Source.
- These constructs return live Databricks data that developers can work with directly from within Visual Studio!
Developer Integration: Databind to Databricks
Connecting Web, Desktop, and Mobile .NET applications with Databricks is just like working with SQL Server. It is even possible to integrate Databricks ADO.NET Provider into applications without writing code.
Developers are free to access the Databricks 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 Databricks 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 Databricks 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 Databricks data with full
read/write (CRUD) support.
Popular ADO Videos:
