Dino Esposito talks about new paging feature in ado.net pdc/march build
public SqlDataReader ExecutePageReader( CommandBehavior behavior, Int32 startRow, Int32 pageSize);
"...Instead, it declares a server cursor on the query and moves it back and forward until you close the reader. Many SQL gurus (including Microsoft's SQL gurus) disagree with this approach."
I also disagree. Sanity talk from Brian R. James :
"I must be missing something. Data-paging is the domain of the stored procedure. Why would I want to transfer thousands of records over the wire to the app server so that ADO.NET can carve up 20 and display them?"
There are many stored procedures written about how to do it right and fast. So this function has to be implemented along with appropriate stored procedures and because of that it is beyond the scope of ado.net. Let us implement it ourselves.
Saturday, May 15, 2004 3:29 AM