Quote:
|
Originally Posted by Devoid
We've recently started a .Net project at work. Unless I'm mistaken, it only transfers your 10k records across the servers once, puts it into a DataSet, and manipulates it there. It's much more efficient than moving stuff all over the place multiple times. I'm no expert, but I think that's how it works.
|
Ok, if that is the case, what if you query returns 10 million records instead of 10 thousand? Logically, with a dataset that size, it would make sense to return the paged data only, right?
If you are using asp.net, storing 10k records in a dataset (bound to a datagrid or something) is going to be a HUGE post back, thus making the end user wait for 10k records worth of viewstate back to the server.
See why it doesn't make sense? There has to be something I am missing and in all my research I have not been able to find it
.
edit: It may be more efficient to hit the database once, but you take a huge hit on the client side. It needs to be balanced out. Thats my opinion anyways.