Skip to main content

Difference between DataSet and DataReader

Data Reader
i) Data Reader is readonly so we can't do any transaction on them.
ii) Data Reader will be the best choice where we need to show the data to the user which requires no transaction.
iii) Data Reader is like a forward only recordset. It fetches one row at a time so very less network cost compare to DataSet(Fethces all the rows at a time). As DataReader is forward only so we can't fetch data randomly.
iv) .NET Data Providers optimizes the datareader to handle huge amount of data.

DataSet
i) DataSet is an in memory representation of a collection of Database objects including tables of a relational database schemas.
ii) DataSet is always a bulky object that requires a lot of memory space compare to DataReader.
iii) DataSet fetches all data from the datasource at a time to its memory area. So we can traverse through the object to get the required data like querying database.
iv) DataSet can have relationship between the fetched tables.

If you feel this tips help you then leave a comment...................
Labels:

Comments

Post a Comment

Popular posts from this blog

What's Virtual DOM?

There’s no big difference between the regular DOM and the virtual DOM. It’s better to think of the virtual DOM as React’s local and simplified copy of the HTML DOM. It allows React to do its computations within this abstract world and skip the real DOM operations, often slow and browser-specific. Real DOM operations are really really expensive. The Virtual DOM is an abstraction of the HTML DOM. It is lightweight and detached from the browser-specific implementation details.  One thing you should remember that the DOM itself was already an abstraction. So, Virtual DOM is an abstraction of an abstraction. :)
Post a Comment
Read more

ASP.NET Dynamic Compilation

In ASP.NET Web Applications, When we request a page it must parse and compile the code of Web Application into one or more assemblies. When the code is compiled, it's translated into a language independent and CPU independent code, that's MSIL code. When we create an ASP.NET page, actually creating the source code for a .NET class. We are creating a new instance of the System.Web.UI.Page class.The entire contents of an ASP.NET page, including all script and HTML content, are compiled into a .NET class. When request an ASP.NET page, ASP.NET Framework checks for a .NET class that corresponds to that page. If a corresponding class does not exist, the Framework automatically compiles the page into a new class and stores the compiled class (the assembly) in the Temporary ASP.NET Files folder. The Temporary ASP.NET files folder located at : \WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files The next time anyone requests the same page in the future, the page is not co...
Post a Comment
Read more