ADO.NET Dataset and ADO Recordset

Arun Choudhary

14y4.4kLearn iOS Programming

Hi
What is the difference between ADO.NET Dataset and ADO Recordset ?

6 Replies

Know the answer? Post it — somebody with the same question will find it here.

Muhammad Imran Ansari4y ago
ADO.NET is an object-oriented set of libraries that allows you to interact with data sources.
Dataset:
Connectionless data holder (It means once we fetched, connection not required) .
We can refer more than 1 table at a time.
We can process more than 1 record
It can represant an entire relationship in database memory can contains with tables and views,relations.
It has no current record pointer.
RecordSet:
Connection oriented Data holder.
It can contains only 1 table is processed at a time.
We have to make travesel to each record and after that We make processing. (It has current record pointer)
geetha geetha4y ago
Dataset:
Dataset is a collection of data tables.
Dataset is a small database because it stores schema and data in application memory area.
It can fetches the data from thedatsource at a time to it's memory area .
You have multiple table inside the dataset, also you can establish the relationship.
Dataset is a disconnected architecture.
dataset can sync the dataset, all the data's are collected from the datbase through the data adapter, and then to fill dataset.
It can provide the feature like storing the data in XML format and loading the data in XML format.
DataRecordset:
Record set is a connection oriented.
Record set can process only one data at a time.
Recordset has the logic for updating and manipulating the data.
Senthilkumar14y ago
Hi Arun,

1.Recordset provides data one row at a time.
Dataset is a data structure which represents the complete table data at same time.

2.Recordset has the logic to update and manipulate data.
Dataset is just a data store and manipulation is done through DataAdapters in .NET.

3.Dataset Disconnected architecture.
Record Set Connected Architecture.

4.With Data set you can retrive data from database like oracle and SQL Server and manage them in one dataset, with recordset this is not possible.

5. All representation of Dataset is using XML while recordset uses COM.

6. The Recordset was not XML-based and could not be serialized to XML easily or flexibly.

7. Recordset can not be transmitted on HTTP while Dataset can be.

8. A DataSet can represent an entire relational database in memory, complete with tables, relations, and views.

9. A DataSet is designed to work without any continuing connection to the original data source.

10. Data in a DataSet is bulk-loaded, rather than being loaded on demand.

11. There's no concept of cursor types in a DataSet.

12. DataSets have no current record pointer You can use For Each loops to move through the data.

13. You can store many edits in a DataSet, and write them to the original data source in a single operation.

14. Though the DataSet is universal, other objects in ADO.NET come in different versions for different data sources

For more info:
http://aspdotnetfordeveloper.blogspot.com/2010/01/what-is-difference-between-dataset-and.html
http://www.netrostar.com/ADO-NET-DataSet-and-ADO-Recordset
Jignesh Trivedi14y ago
hi,

please refer

http://msdn.microsoft.com/en-us/library/904fck4k%28v=vs.71%29.aspx
if is very good article on same.
Sam Hobbs14y ago
They are not comparable. A recordset is for a table and a dataset is for a database (multiple tables). Right?

I do not know what the unmanged equivalent is to the managed (.Net) DataSet class; I think there is not one. The ADO .Net DataSet class contains relationships as well as DataTables in memory and as far as I know unmanaged ADO does not do that.
Satyapriya Nayak14y ago
Hi Shubham,

Differences between ADO Recordset and ADO.Net DataSet:

1. Table Collection: ADO Recordset provides the ability to navigate through a single table of information. That table would have been formed with a join of multiple tables and returning columns from multiple tables. ADO.NET DataSet is capable of holding instances of multiple tables. It has got a Table Collection, which holds multiple tables in it. If the tables are having a relation, then it can be manipulated on a Parent-Child relationship. It has the ability to support multiple tables with keys, constraints and interconnected relationships. With this ability the DataSet can be considered as a small, in-memory relational database cache.

2. Navigation: Navigation in ADO Recordset is based on the cursor mode. Even though it is specified to be a client-side Recordset, still the navigation pointer will move from one location to another on cursor model only. ADO.NET DataSet is an entirely offline, in-memory, and cache of data. All of its data is available all the time. At any time, we can retrieve any row or column, constraints or relation simply by accessing it either ordinarily or by retrieving it from a name-based collection.

3. Connectivity Model: The ADO Recordset was originally designed without the ability to operate in a disconnected environment. ADO.NET DataSet is specifically designed to be a disconnected in-memory database. ADO.NET DataSet follows a pure disconnected connectivity model and this gives it much more scalability and versatility in the amount of things it can do and how easily it can do that.

4. Marshalling and Serialization: In COM, through Marshalling, we can pass data from 1 COM component to another component at any time. Marshalling involves copying and processing data so that a complex type can appear to the receiving component the same as it appeared to the sending component. Marshalling is an expensive operation. ADO.NET Dataset and DataTable components support Remoting in the form of XML serialization. Rather than doing expensive Marshalling, it uses XML and sent data across boundaries.

5. Firewalls and DCOM and Remoting: Those who have worked with DCOM know that how difficult it is to marshal a DCOM component across a router. People generally came up with workarounds to solve this issue. ADO.NET DataSet uses Remoting, through which a DataSet / DataTable component can be serialized into XML, sent across the wire to a new AppDomain, and then Desterilized back to a fully functional DataSet. As the DataSet is completely disconnected, and it has no dependency, we lose absolutely nothing by serializing and transferring it through Remoting.

Also refer

http://msdn.microsoft.com/en-us/library/904fck4k%28v=vs.71%29.aspx

http://www.netrostar.com/ADO-NET-DataSet-and-ADO-Recordset

Thanks