This question is locked. New answers and comments are not allowed.
Hey,
While following the example about KendoUI integration I'm running into an issue that each $orderby DESC query leads to very slow repsonse times from the server.
Datasource is a simple 1.000.000 record people table with an non-clustered index on LastName. Initial return of an unsorted result set is fast, sorting it ASC is fast as well. Using profiler I can see that in addition to the a.[LastName] DESC an a.[PeopleId] is added.
Comparing the two attached execution plans you can see that adding a.[PeopleId] to a DESC query makes the query inefficient.
As I'm pretty new to OpenAccess ORM it's probably me doing something wrong in my setup. What would be the recommend way to fine tune the generated sp_prepexec expressions.
Thanks,
Rainer
While following the example about KendoUI integration I'm running into an issue that each $orderby DESC query leads to very slow repsonse times from the server.
Datasource is a simple 1.000.000 record people table with an non-clustered index on LastName. Initial return of an unsorted result set is fast, sorting it ASC is fast as well. Using profiler I can see that in addition to the a.[LastName] DESC an a.[PeopleId] is added.
Comparing the two attached execution plans you can see that adding a.[PeopleId] to a DESC query makes the query inefficient.
As I'm pretty new to OpenAccess ORM it's probably me doing something wrong in my setup. What would be the recommend way to fine tune the generated sp_prepexec expressions.
Thanks,
Rainer