DataReader creates too much traffic and database queries?
Posted on 2012-03-28
The need to know:
Since the debate is so great for the DataReader and filling a GridView control instead of a Dataset, why are developers suggesting a GridView, is it because it can hold all the data in memory while being able to make use of the many GridView features?
I know I can fill the simpler controls directly, I have actually done so, but the problem that I see with using the DataReader only, is that with my complex Stored Procedure that brings a "large" amount of data over to the web Client, it will need to connect to the Database Server each time I need to access the data, and each time the complex Stored Procedure will need to run. So isn't this a bit expensive if you're not making use of caching to store the data in memory, since the Database Server will now have much more traffic than if the web Client could make use of a Disconnected Dataset?
Does the DataReader create too much traffic and to many database queries?