|
|
|
|
We are specialists in .NET technology |
- ASP.NET web development
- .NET Windows software development
- .NET component development
- .NET XML web service development

|
|
|
|
|
|
|
|
ADO.NET is the data access model for .NET applications. It can be used to access relational database systems such as SQL Server 2000, and many additional data sources for which there is an OLE DB provider. To a certain extent, ADO.NET represents the latest evolution of ADO technology. However, ADO.NET introduces some major changes and innovations specifically aimed at the loosely coupled, and inherently disconnected, nature of Web applications. |
|
|
|
|
|
|
| The ADO.NET architecture can be divided into two logical pieces:
command execution and caching. Command execution requires features like
connectivity, execution, and reading of results. These features are enabled
with .NET data providers. Caching of results is handled by the DataSet.

|
|
|
|
|
|
|
|
For the majority of data access operations, ADO.NET performance is significantly
improved over ADO and OLE DB. These performance improvements can be attributed
to the following factors:
-
ADO.NET and its classes are built upon and managed by the Common Language
Runtime (CLR). Therefore, ADO.NET indirectly benefits from improvements in
memory management, type conversion, object pooling, and various other low level
performance enhancements.
-
A new provider model enables explicit, stream-based access to data sources. For
example, the SQL Server .NET Data Provider was built to deal with SQL Server
data types in a native manner.
-
A simplified and disconnected object model. By removing cursor support and
minimizing the object model result sets can be processed in a more efficient
manner with fewer resources.
|
|
|
|
|
|