Cassandra ADO.NET Provider

Read, Write, and Update Cassandra from .NET Apps.

Easily connect Apache Cassandra with BI, ETL, Reporting, and Custom Apps.

  download   buy now

Other Technologies

Cassandra Logo

The Cassandra ADO.NET Data Provider enables user to easily connect to Cassandra data from .NET applications. Connect .NET applications with the Cassandra real-time NoSQL cloud database service. Use Apache Cassandra as the big data backend that powers your .NET applications.


  • Cassandra 2.0 through 3.0 Compatibility – Leverages the faster performance and improved security of Cassandra V3.0.
  • CQL Pass-through Capability – Delivers native CQL3 or CQL2 data access to clustered Cassandra data, enabling users to create queries in CQL or SQL
  • Enables SQL-92 capabilities on Apache Cassandra NoSQL data.
  • Flexible NoSQL flattening - automatic schema generation, flexible querying etc.
  • Connect to live Apache Cassandra data, for real-time data access
  • Full support for data aggregation and complex JOINs in SQL queries
  • Seamless integration with leading BI, reporting, and ETL tools and with custom applications


  • DataBind to Cassandra using standard Visual Studio wizards.
  • Comprehensive support for CRUD (Create, Read, Update, and Delete).
  • Supports ADO.NET Entity Framework (EF 5 & 6), LINQ to Datasets, etc.
  • Full Unicode support for data, parameter, & metadata.
  • Support for 32-bit and 64-bit operating systems.
  • Supports .NET Framework 4.0+ and .NET Standard 2.0 (.NET Core 2.1+, .NET 6.0).


225+ ADO.NET Drivers For Real-Time BI & Reporting.

Where can I use the Cassandra ADO.NET Provider?

ADO.NET Access to Apache Cassandra

Full-featured and consistent SQL access to any supported data source through ADO.NET

  • Fully-managed .NET

    100% fully managed ADO.NET libraries supporting .NET Standard, .NET Core 2.0, & Xamarin.

  • Developer Friendly

    Seamless integration with all versions of Visual Studio.

  • Powerful ADO.NET Features

    Including support for ADO.NET Entity Framework (EF 5 & 6), ADO.NET 2.0, LINQ to Datasets, etc.

  • Replication and Caching

    Our replication and caching commands make it easy to copy data to local and cloud data stores such as Oracle, SQL Server, Google Cloud SQL, etc. The replication commands include many features that allow for intelligent incremental updates to cached data.

  • String, Date, Numeric SQL Functions

    The driver includes a library of 50 plus functions that can manipulate column values into the desired result. Popular examples include Regex, JSON, and XML processing functions.

  • Collaborative Query Processing

    Our drivers enhance the data source's capabilities by additional client side processing, when needed, to enable analytic summaries of data such as SUM, AVG, MAX, MIN, etc.

  • Easily Customizable and Configurable

    The data model exposed by our ADO.NET Providers can easily be customized to add or remove tables/columns, change data types, etc. without requiring a new build. These customizations are supported at runtime using human-readable schema files that are easy to edit.

  • Secure Connectivity

    Includes standard Enterprise-class security features such as TLS/ SSL data encryption for all client-server communications.

Standard ADO.NET Access to Cassandra

The Cassandra ADO.NET Provider offers the most natural way to access Cassandra data from any .NET application. Simply use Cassandra Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the Cassandra 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 Apache Cassandra 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 Cassandra Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: CassandraConnection, CassandraCommand, CassandraDataAdapter, CassandraDataReader, CassandraDataSource, CassandraParameter, etc. Because of this you can now access Cassandra data in an easy, familiar way.

For example:

using (CassandraConnection conn = new CassandraConnection("...")) {
	string select = "SELECT * FROM CQL Queries";
	CassandraCommand cmd = new CassandraCommand(select, conn);
	CassandraDataAdapter adapter = new CassandraDataAdapter(cmd);
	using (adapter) {
		DataTable table = new DataTable();

More Than Read-Only: Full Update/CRUD Support

Cassandra 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 Cassandra Data Provider as easily as interacting with a database table.

using (CassandraConnection connection = new CassandraConnection(connectionString)) {
	CassandraDataAdapter dataAdapter = new CassandraDataAdapter(
	"SELECT Id, Where FROM CQL Queries", connection);
	dataAdapter.UpdateCommand = new CassandraCommand(
		"UPDATE CQL Queries SET Where = @Where " +
		"WHERE Id = @ID", connection);

	dataAdapter.UpdateCommand.Parameters.AddWithValue("@Where", "Where");
	dataAdapter.UpdateCommand.Parameters.AddWithValue("@Id", "80000173-1387137645");

	DataTable CQL QueriesTable = new DataTable();
	dataAdapter.Fill(CQL QueriesTable);

	DataRow firstrow = CQL QueriesTable.Rows[0];
	firstrow["Where"] = "New Location";

	dataAdapter.Update(CQL QueriesTable);

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:

  1. Network Connections - Slow network connections and latency issues are common in mobile applications.
  2. Service Delays - Delays due to service interruptions, resulting in server hardware or software updates.
  3. Large Data - Intentional or unintentional requests for large amounts of data.
  4. Disconnects - Complete loss of network connectivity.

The CData ADO.NET Provider for Apache Cassandra solves many of these issues with support for replication queries that can be used to sync data to local databases, greatly improving the performance and dramatically reduce application bottlenecks.

More information about ADO.NET Provider performance capabilities are available in the included documentation.

Visual Studio Integration & Server Explorer

Working with the new Cassandra ADO.NET Provider is easy. As a fully-managed .NET Data Provider, the Cassandra Data Provider integrates seamlessly with the Visual Studio development environment as well as any .NET application.

As an ADO.NET Data Provider, Cassandra ADO.NET Provider can be used to access and explore Apache Cassandra data directly from the Visual Studio Server Explorer.

It's easy. As a standard ADO.NET adapter, developers can connect the Server Explorer to Cassandra ADO.NET Provider just like connecting to any standard database.

  • Add a new Data Connection from the Server Explorer and select the Apache Cassandra Data Source

  • Configure the basic connection properties to access your Apache Cassandra account data.

Explore all of the data available! Cassandra ADO.NET Provider makes it easy to access live Apache Cassandra data from Visual Studio.

  • After configuring the connection, explore the feeds, views, and services provided by the Apache Cassandra Data Source.
  • These constructs return live Apache Cassandra data that developers can work with directly from within Visual Studio!

Developer Integration: Databind to Cassandra

Connecting Web, Desktop, and Mobile .NET applications with Apache Cassandra is just like working with SQL Server. It is even possible to integrate Cassandra ADO.NET Provider into applications without writing code.

Developers are free to access the Cassandra 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 Apache Cassandra 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 Apache Cassandra 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 Apache Cassandra data with full read/write (CRUD) support.