Answer / pankaj

1. Business Model


ADO is Connection-oriented Models used mostly
ADO.NET is Disconnected models are used:Message-like Models.


2. Disconnected Access

ADO Provided by Record set.
ADO.NET Provided by Data Adapter and Data set

3. XML Support

ADO Limited
ADO.NET Robust Support

4. Connection Model

ADO Client application needs to be connected always to
data-server while working on the data, unless using
client-side cursors or a disconnected Record set

ADO.NET Client disconnected as soon as the data is
processed. DataSet is disconnected at all times.

5. Data Passing

ADO objects communicate in binary mode.
ADO.NET uses XML for passing the data.

Answer / sweety

diff:
1.ADO is a connected approach,where as ADO.Net is a
disconnected data approach.
2.ADO is a concept of vb 6.0,where as ADO.Net ia concept
of .Netframework.
3.ADO is a Object Based,where as ADO.Net is a Object
Oriented.
4.ADO supports recordset,whereas ADO.Net supports dataset.

Answer / sabir

ado.net is xml based and ado is com based
here easy to implement he disconnected model and diffcivult
to

Answer / bastin

1.ADO is a connected approach,where as ADO.Net is a
disconnected data approach.
2.ADO is a concept of vb 6.0,where as ADO.Net ia concept
of .Netframework.
3.ADO is a Object Based,where as ADO.Net is a Object
Oriented.
4.ADO supports recordset,whereas ADO.Net supports dataset.

Answer / satyambabu

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. With ADO, all the
data is contained in a recordset object which had problems
when implemented on the network and penetrating firewalls.
ADO was a connected data access, which means that when a
connection to the database is established the connection
remains open until the application is closed. Leaving the
connection open for the lifetime of the application raises
concerns about database security and network traffic. Also,
as databases are becoming increasingly important and as
they are serving more people, a connected data access model
makes us think about its productivity. For example, an
application with connected data access may do well when
connected to two clients, the same may do poorly when
connected to 10 and might be unusable when connected to 100
or more. Also, open database connections use system
resources to a maximum extent making the system performance
less effective.

Answer / bhavesh

ADO.NET is stateless mechanism. I can treat the ADO.Net as a
separate in-memory database where in I can use relationships
between the tables and select insert and updates to the
database. I can update the actual database as a batch.

Answer / thiyagu.p

ADO : Needs contionous connection to read records.

ADO.NET : It reads entire results and keep it the form of
table. So it never re-connect with DB.

Which is faster entity framework or ado.net?

0 Answers  

What are the Features and disadvantages of dataset

0 Answers   Microsoft,

How to check if the Dataset has records ?

0 Answers   NA,

What property must be set and what method must be called in your code to bind the data from some data source to the Repeater control?

0 Answers  

Explain how to pass multiple tables in datasets simultaneously?

0 Answers  

What is the purpose of using adodb?

0 Answers  

What is an ADO.Net?

0 Answers  

Define connection string?

0 Answers  

Define the data provider classes that is supported by ado.net?

0 Answers  

Which method do you invoke on the DataAdapter control to load your generated dataset with data?

4 Answers  

How would u connect to database using .NET?

5 Answers   TCS, Tesco,

How to enable and disable connection pooling?

0 Answers