Standard ADO.NET Access to Azure Data Lake Storage
The Azure Data Lake Storage ADO.NET Provider offers the most natural way to access Azure Data Lake Storage data from any
.NET application. Simply use Azure Data Lake Storage Data Provider objects to connect and access data just as you
would access any traditional database. You will be able to use the Azure Data Lake Storage 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 Azure Data Lake Storage 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 Azure Data Lake Storage Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server
and OLEDB, including: Azure Data Lake StorageConnection, Azure Data Lake StorageCommand, Azure Data Lake StorageDataAdapter, Azure Data Lake StorageDataReader,
Azure Data Lake StorageDataSource, Azure Data Lake StorageParameter, etc. Because of
this you can now access Azure Data Lake Storage data in an easy, familiar way.
For example:
using (Azure Data Lake StorageConnection conn = new Azure Data Lake StorageConnection("...")) {
string select = "SELECT * FROM ADLSData";
Azure Data Lake StorageCommand cmd = new Azure Data Lake StorageCommand(select, conn);
Azure Data Lake StorageDataAdapter adapter = new Azure Data Lake StorageDataAdapter(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 Azure Data Lake Storage 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 Azure Data Lake Storage ADO.NET Provider is easy. As a fully-managed .NET Data Provider, the Azure Data Lake Storage Data Provider
integrates seamlessly with the Visual Studio development environment as well as any .NET application.
As an ADO.NET Data Provider, Azure Data Lake Storage ADO.NET Provider can be used to access and explore
Azure Data Lake Storage data directly from the Visual Studio Server Explorer.
It's easy. As a standard ADO.NET adapter, developers can connect the Server Explorer to Azure Data Lake Storage ADO.NET Provider
just like connecting to any standard database.
- Add a new Data Connection from the Server Explorer and select the Azure Data Lake Storage Data Source
- Configure the basic connection properties to access your Azure Data Lake Storage account data.
Explore all of the data available! Azure Data Lake Storage ADO.NET Provider makes it easy to access live Azure Data Lake Storage data from Visual Studio.
- After configuring the connection, explore the feeds, views, and services provided by the Azure Data Lake Storage Data Source.
- These constructs return live Azure Data Lake Storage data that developers can work with directly from within Visual Studio!
Developer Integration: Databind to Azure Data Lake Storage
Connecting Web, Desktop, and Mobile .NET applications with Azure Data Lake Storage is just like working with SQL Server. It is even
possible to integrate Azure Data Lake Storage ADO.NET Provider into applications without writing code.
Developers are free to access the Azure Data Lake Storage 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 Azure Data Lake Storage 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 Azure Data Lake Storage 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 Azure Data Lake Storage data with full read/write (CRUD) support.
