Asp.net developer uses DataSet and DataReader to fetch data from the data source while developing asp.net application. But most of them don’t know exactly what are the main difference between DataSet and DataReader and what to use and when to use out of these two.
Both DataSet and DataReader are widely used in asp.net applications for the same purpose i.e. to get/fetch the data from the database. But one has to know the best practices in developing fast, reliable and scalable application. So I have tried to list some main differences between the DataSet and DataReader which are as follows:
1. DataReader is used to retrieve read-only (cannot update/manipulate data back to datasource) and forward-only (cannot read backward/random) data from a database. It provides the ability to expose the data from database while DataSet is a collection of in-memory tables.
2. DataReader fetches the records from database and stores in the network buffer and gives whenever requests. It releases the records as query executes and do not
wait for the entire query to execute. Hence very fast as compare to the DataSetwhich releases the data after loading all the data in memory.
3. DataReader is like a forward only recordset. It fetches one row at a time so very less network cost compare to DataSet which fetches all the rows at a time i.e. it fetches all data from the datasource at a time to its memory area.
4. As one row at a time is stored in memory in DataReader it increases application performance and reduces system overheads while there is more system overheads in DataSet as it fetches all the data from the datasource at a time in memory.
5. As DataReader is forward only, we can’t fetch random records as we can’t move back and forth .While in DataSet we can move back and forth and fetch records randomly as per requirement.
6. DataReader fetches data from a single table while DataSet can fetch data from multiple tables.
7. As DataReader can have data from a single table so no relationship can be maintained while relationship between multiple tables can be maintained inDataSet.
8. DataReader is read only so no transaction like insert, update and delete is possible while these transactions are possible in DataSet.
9. DataSet is a bulky object that requires lot of memory space as compared toDataReader .
10. DataReader is a connected architecture: The data is available as long as the connection with database exists while DataSet is a disconnected architecture that automatically opens the connection, fetches the data into memory and closes the connection when done.
11. DataReader requires connection to be open and close manually in code while DataSet automatically handles it.
12. DataSet can be serialized and represented in XML so easily passed around to other tiers but DataReader can't be serialized.
13. DataReader will be the best choice where we need to show the data to the user which requires no manipulation while DataSet is best suited where there is possibility of manipulation on the data.
14. Since DataSet can be serialized it, can be used in wcf services and web service that will return retrieved data. But DataReader can’t be serialized so can’t be used in wcf services and web services.
15. When you need to navigate through the data multiple times then DataSet is better choice e.g. we can fill data in multiple controls But DataReader can only be read once so it can be bound to a single control and requires data to be retrieved for each control.
No comments:
Post a Comment