web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Is READ_COMMITTED_SNAPSHOT = on required or recommended setting for SQL?

(0) ShareShare
ReportReport
Posted on by 860

We have been having issues lately with CRM due to sql blocking.  After doing some digging, I ran across this article.  It mentions the AX product, rather than just regular CRM, but Im curious if this applies or not?

http://blogs.msdn.com/b/axsupport/archive/2011/09/22/severe-sql-locking-and-blocking-on-dynamics-ax.aspx?Redirected=true

In our case, this setting is off...so if this applies, it might explain why the constant blocking that comes up during even moderate load

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Peter72 Profile Picture
    1,815 on at

    Not officially, but a common recommendation (also directly from MS) to improve performance and reduce db-locks.

    Regards,

    Peter

  • Suggested answer
    Josh Thompson Profile Picture
    1,115 on at

    RCSI isn't a setting to improve performance. If you are going to turn on RCSI you need to understand the implications if doing so. It will greatly increase the load on your tempdb and you need to account for that. Every row in your db is versions with RCSI it is NOT the same as setting transaction isolation level = read committed.

    Here is a brief article about RCSI you should read and understand. msdn.microsoft.com/.../tcbchxcb(v=vs.110).aspx

    I would also look to understand what your blocking issue is caused by. Is it a particular table? User? Application? Time of day?

  • Peter72 Profile Picture
    1,815 on at

    Josh, I totally agree with your statement.

    My answer was a bit short, and I know the article you mentioned.

    And yes, first of all you should find the root cause of the blocking issue(s) and resolve them if possible.

    However, in some cases we saw massive performance improvements. Mostly when a lot of scheduled interface jobs and/or a lot of plugins worked on the same entities.

    Regards, Peter

  • Josh Thompson Profile Picture
    1,115 on at

    Peter, my reply was more directed at the OP than you, sorry if it came across the other way around.

  • Peter72 Profile Picture
    1,815 on at

    Josh, don't worry, I did not construed it this way :-)

    Best Regards

    Peter

  • bitshift Profile Picture
    860 on at

    This article on Technet as part of other Dynamics CRM-specific optimization steps, suggests enabling Read Committed Snapshot isolation to avoid deadlocks

    social.technet.microsoft.com/.../13661.dynamics-crm-2011-quick-optimization-guide.aspx

  • Verified answer
    Peter72 Profile Picture
    1,815 on at

    I confirm that we could reduce the number of deadlocks significantly by that. But as Josh mentioned, you should try to find out and eliminate the root cause. In our project, some long running interfaces (built with Scribe) causes these deadlocks.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans