Thursday, 7 September 2017

{know-how} MSCRM FetchXML SSRS - Improve performance with No-Lock - FetchXML Nolock



A quick tip around improving CRM data retrieval performance using fetchxml, this is applicable to both RetrieveMultiple  and SSRS performance.

What is no-lock?
Whenever we query CRM using fetchxml,a lock is issued against the table. when we use No-lock the process of issuing lock is skipped. This type of data retrieval is also called as dirty read because there is a chance that you might read the uncommitted data before rollback.

Advantage?

  • Improves SSRS report performance or RetrieveMultiple performance on high transaction oriented tables


Example:

<fetch mapping="logical" no-lock="true" >
    <entity name="account" />
</fetch> 

No comments:

Post a Comment

Contact Form

Name

Email *

Message *