I was reading about some new features of ADO.NET 2.0 and, when reading about the new ExecutePageReader method, a question comes in my mind...
Normally, for paging I currently use stored procedures with temporary tables that pages data with the ROWCOUNT I want (I pass it as a parameter to the stored procedure).
This new method obviously simplifies me the work: the paging is done by the method and I've not to write SQL Code on my stored to to the paging task... wow... 
but... the ExecutePageReader method use server cursors and I'm not sure this is a more efficient way for paging than the SQL Server way (stored). Is there a real advantage on performance or not? I'm not so sure...
However, I've listen from a friend of mine that maybe ExecutePageReader will be dropped from the future... is it true? And why? I think that it could be a useful method however... no drop it please!