Hi,
We are using RadGrid with EntityDatasource. We have pagination enabled on the RadGrid.
We loooked at the sql profiler and saw that RadGrid makes two calls to the database (through EntityDatasource). One call is for getting the total count (for displaying pages and count) and the second is for fetches actual records in the page.
Later when we move to the second page, I can see in the sql profiler that again two calls are made - one for count and other for all the rows of the second page.
Can we configure the radgrid such that it does not fetch the count on second or subsequent operations (like moving to next page or sorting)? Since the grid already has the total count whcih it gets on the first load, cant the radgrid maintian this and use this in the subsequent operations?
Thanks and Regards,
Bhaskar Shanbhag
PS. I am asking this question since our sql query which we use in the Entity Datasource is already very slow and calling it two times for every operation makes it slower.
We are using RadGrid with EntityDatasource. We have pagination enabled on the RadGrid.
We loooked at the sql profiler and saw that RadGrid makes two calls to the database (through EntityDatasource). One call is for getting the total count (for displaying pages and count) and the second is for fetches actual records in the page.
Later when we move to the second page, I can see in the sql profiler that again two calls are made - one for count and other for all the rows of the second page.
Can we configure the radgrid such that it does not fetch the count on second or subsequent operations (like moving to next page or sorting)? Since the grid already has the total count whcih it gets on the first load, cant the radgrid maintian this and use this in the subsequent operations?
Thanks and Regards,
Bhaskar Shanbhag
PS. I am asking this question since our sql query which we use in the Entity Datasource is already very slow and calling it two times for every operation makes it slower.