ADO.NET Provider Overview
The Amazon SimpleDB ADO.NET Provider offers the most natural way to access SimpleDB data from any .NET application. Simply use Amazon SimpleDB Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the Amazon SimpleDB Data Provider through Visual Studio Server Explorer, in code through familiar classes, and in data controls like DataGridView, GridView, DataSet, etc.
Using the Amazon SimpleDB Data Provider
The Amazon SimpleDB Data Provider wraps the complexity of accessing SimpleDB services in an easy-to-integrate, fully managed ADO.NET Data Provider. Applications then access SimpleDB through the Amazon SimpleDB Data Provider with simple Transact-SQL.
The CData ADO.NET Provider for Amazon SimpleDB 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 Amazon SimpleDB Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: SimpleDBConnection, SimpleDBCommand, SimpleDBDataAdapter, SimpleDBDataReader, SimpleDBDataSource, SimpleDBParameter, etc. Because of this you can now access SimpleDB data in an easy, familiar way.
(SimpleDBConnection conn =
"SELECT * FROM SimpleDBTable"
SimpleDBCommand cmd =
SimpleDBDataAdapter adapter =
DataTable table =
More Than Read-Only: Full Update/CRUD Support
Amazon SimpleDB 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 Amazon SimpleDB Data Provider as easily as interacting with a database table.
(SimpleDBConnection connection =
SimpleDBDataAdapter dataAdapter =
"SELECT Id, Where FROM SimpleDBTable"
"UPDATE SimpleDBTable SET Where = @Where "
"WHERE Id = @ID"
DataTable SimpleDBTableTable =
DataRow firstrow = SimpleDBTableTable.Rows;
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 Amazon SimpleDB solves these issues by supporting powerful smart cachingtechnology that can greatly improve the performance and dramatically reduce application bottlenecks.
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.