I have a query that returns many thousands of records, a broad search
result. The web interface is fine with it because I use a paged grid view -
however this control cannot tell the app server to just return the records
that it's going to dispaly, it returns the whole result set, which large
enough to cause a communication performance problem between the app server
and the web server.
SO...
I really want to be sure that there isn't some existing, built-in design
structure I can use before I go re-invent the wheel, put paging into the web
method, or the query itself. What's the most commonly accepted practice?
Paul
Eliyahu Goldin - 11 Feb 2008 15:15 GMT
For large recordsets the practice is to put paging into the query itself.

Signature
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net
>I have a query that returns many thousands of records, a broad search
>result. The web interface is fine with it because I use a paged grid view -
[quoted text clipped - 11 lines]
>
> Paul