This question is locked. New answers and comments are not allowed.
Apologies if this is a dumb question but...
I have a page with an OADataSource and see that when hooked up to a RadGrid in full design mode with paging enabled it performs well and the queries that hit SQL2005 restrict the network traffic (ie it doesn't pull back all the rows every time and even when viewing pages later on in the dataset it only actually returns the ones you want).
However if I implement a Best Practice BLL/BO/DB/Persistent Classes project with those layers and hook up a RadGrid in code (is there a way to do it thru the designer?) to the GetList() method - it will call that and this means the database will /always/ pull back all the records into my DB class :( THis seems to me to diminish the attraction. I need to provide efficient paging across around 50,000 rows (under extreme circumstances)
Is there any way to get the performance of the OA data source but still use the proper layered approach?
Is there any support planned for enhanced paging in SQL2008?
Thanks for input,
Mark
I have a page with an OADataSource and see that when hooked up to a RadGrid in full design mode with paging enabled it performs well and the queries that hit SQL2005 restrict the network traffic (ie it doesn't pull back all the rows every time and even when viewing pages later on in the dataset it only actually returns the ones you want).
However if I implement a Best Practice BLL/BO/DB/Persistent Classes project with those layers and hook up a RadGrid in code (is there a way to do it thru the designer?) to the GetList() method - it will call that and this means the database will /always/ pull back all the records into my DB class :( THis seems to me to diminish the attraction. I need to provide efficient paging across around 50,000 rows (under extreme circumstances)
Is there any way to get the performance of the OA data source but still use the proper layered approach?
Is there any support planned for enhanced paging in SQL2008?
Thanks for input,
Mark