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

Microservices vs. APIs

It still surprises me just how many times I come across misconceptions around Micro Services and APIs. Often hearing phrases like micro services are fine grained web services or API is themselves are equivalent to micro services. These all sort of show fundamental misconceptions under the covers. So, I've written this just to really break that out and explain about what the key differences are in those two concepts. What is an API? An API, fundamentally Application Programming Interface, that is an interface. It's a way of making requests into a component. So it's the route that you go in to make those requests. In modern use that typically means a REST API, that's a call made using HTTP protocol using JSON data as the payload. What are Micro Services? So let's ensure we also have a clear crisp definition on what a micro service architecture really is. Micro-Services architecture is about breaking down large silo applications into smalle...
Post a Comment
Read more

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