Answer the question
In order to leave comments, you need to log in
How can I force CRM to generate _Quick_Find_ requests with nolock, which will be everywhere?
"Quick" requests are formed on the basis of fetch (some kind of xml bike for request description). You can add a flag to this bicycle that the request should be executed in dirty read mode. The irony is that the nolock hint is applied only to the main view to which the from is made. And if there is a check, for example, for child records, then complete idiocy is done:
select .... from AcountBase whith (nolock) where ParentId in (select ID from AcountBase where ....)
If you open the profiler, it turns out that they are stuffed with such constructions _Quick_Find_ queries. Due to the presence of a bunch of business processes with sp_getapplock, the search works depressingly.
How can I force CRM to generate _Quick_Find_ requests with nolock, which will be everywhere?
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question