Wednesday, December 29, 2010 | | 0 comments

ADO.NET Objects

The SqlConnection Object
The SqlCommand Object
The SqlDataReader Object
The Dataset Object
The SqlDataAdapter Object

| | 0 comments

Data provider

We know that ADO.NET allows us to interact with different types of data sources and different types of databases. However, there isn't a single set of classes that allow you to accomplish this universally. Since different data sources expose different protocols, we need a way to communicate with the right data source using the right protocol. Some older data sources use the ODBC protocol, many newer data sources use the OleDb protocol, and there are more data sources every day that allow you to communicate with them directly through .NET ADO.NET class libraries.
ADO.NET provides a relatively common way to interact with data sources, but comes in different sets of libraries for each way you can talk to a data source. These libraries are called Data Providers and are usually named for the protocol or data source type they allow you to interact with.

| | 0 comments

| | 0 comments

Data Provider is a set of components including:

The Connection object (SqlConnection, OleDbConnection, OdbcConnection,OracleConnection)
The Command object (SqlCommand, OleDbCommand, OdbcCommand, OracleCommand)
The DataReader object (SqlDataReader, OleDbDataReader, OdbcDataReader,OracleDataReader)
And the DataAdapter object (SqlDataAdapter, OleDbDataAdapter, OdbcDataAdapter,OracleDataAdapter).

| | 0 comments

.NET Framework data providers

Data Provider for SQL Server (System.Data.SqlClient).
Data Provider for OLEDB (System.Data.OleDb).
Data Provider for ODBC (System.Data.Odbc). 

Data Provider for Oracle (System.Data.OracleClient).

| | 0 comments

Evolution of ADO.NET

The first data access model, DAO (data access model) was created for local databases with the built-in Jet engine which had performance and functionality issues. Next came RDO (Remote Data Object) and ADO (Active Data Object) which were designed for Client Server architectures but, soon ADO took over RDO. ADO was a good architecture but as the language changes so is the technology

| | 0 comments

Understanding ADO.NET

In organizations, business applications need to the data. Data is stored in a relational database in the form of related tables.
Retrieving and manipulating data directly from a database requires the knowledge of database commands. this may at times become a limitation because everyone may not be conversant with database commands. for example, updating the data stored in a SQl server database may not be convenient for a person who does not know DML (Data manipulation language) commands or statements 

To overcome this limitation ,business application allow users to retrieve data stored in a database and present it in a user-friendly interface, without having to write database commands. the user can even add, delete and update database records directly from these applications.

| | 0 comments

Why ADO.NET?

Likewise, if a database is Updated, the connection is opened long enough to complete the Update operation and is closed. By keeping connections open for only a minimum period of time, ADO .NET conserves system resources and provides maximum security for databases and also has less impact on system performance.
Also, ADO .NET when interacting with the database uses XML and converts all the data into XML format for database related operations making them more efficient.
napplication interacts with the database, the connection is opened to serve the request of the application and is closed as soon as the request is completed.

| | 0 comments

 What is ADO.NET

ADO.NET is the new database technology of the .NET (Dot Net) platform, and it builds on Microsoft ActiveX� Data Objects (ADO).
ADO is a language-neutral object model that is the keystone of Microsoft's Universal Data Access strategy. ADO.NET is an integral part of the .NET Compact Framework, providing access to relational data, XML documents, and application data. ADO.NET supports a variety of development needs. You can create database-client applications and middle-tier business objects used by applications, tools, languages or Internet browsers
ADO.NET is a set of computer software components that programmers can use to access data and data services. It is a part of the base class library that is included with the Microsoft .NET Framework
It is commonly used by programmers to access and modify data stored in relational database systems, though it can also access data in non-relational sources.
 ADO.NET is sometimes considered an evolution of ActiveX Data Objects (ADO) technology, but was changed so extensively that it can be considered an entirely new product.

| | 0 comments

ADO.NET comming soon..................