What is ADO.NET?
ADO.NET is the data access component for the .NET Framework.
ADO.NET leverages the power of XML to provide disconnected access to data. ADO.NET is made of a set of classes that are used for connecting to a database, providing access to relational data, XML, and application data, and retrieving results. ADO.NET data providers contain classes that represent the provider's Connection, Command, DataAdapter and DataReader objects (among others).
How Does ADO.NET Work?
ADO.NET makes it possible to establish a connection with a data source, send queries and update statements to the data source, and process the results.
ADO.NET has several key components:
Application or component; processes and calls ADO.NET functions to submit SQL statements and retrieve results.
DataSet; as in-memory cache of data which functions like a disconnected XML data cache. The overall functions of the DataSet closely recall those of an in-memory database. The DataSet is designed to run in the application space wherever the logic requires local data. This helps increase scalability of systems by reducing load on the major database backends and enabling local processing of data across whatever tier the application requires. For flexibility, the DataSet provides XML and relational interfaces of the data to the developer.
DataReader; which provides a direct, read-only SQL interface to the backend. The DataReader is a component of the data provider.
ADO.NET Data Provider; connects an ADO.NET application to the backend data store. The data provider comprises the Connection, Command, DataReader and DataAdapter objects. The data provider supplies connection information through the Connection object.
Why Do Application Developers Need ADO.NET?
ADO.NET provides a comprehensive caching data model for marshalling data between applications and services with facilities to optimistically update the original data sources. This enables developer to begin with XML while leveraging existing skills with SQL and the relational model.
Although the ADO.NET model is different from the existing ADO model, the same basic concepts include provider, connection and command objects. By combining the continued use of SQL with similar basic concepts, current ADO developers should be able to migrate to ADO.NET over a reasonable period of time.
Shashi Ray