Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Isolation Level (RCSI – Read Committed Snapshot Isolation)
Check if the database of Dynamics 365 CE organization is set READ_COMMITTED_SNAPSHOT to ON. When it is set to OFF, locking contention can adversely impact the performance of Microsoft SQL Server. READ COMMITTED ISOLATION can be used to minimize potential locking contention while protecting transactions from “dirty” reads of uncommitted data modifications. With dirty reads, data within the current transaction can potentially be modified by other transactions between individual statements, resulting in non-repeatable reads or phantom data.
Set by default during a standard installation of Microsoft SQL Server, READ COMMITTED isolation specifies that statements cannot read data that has been modified but not committed by other transactions. With READ_COMMITTED_SNAPSHOT set to ON, the Database Engine uses row versioning to present each statement with a transactionally consistent snapshot of the data as it existed at the start of the statement. Locks are not used to protect the data from updates by other transactions.
Considerations for documentation purposes
NOTE: It is important to consider possible adverse effects of enabling RCSI before implementing the change below. It is strongly recommended to work with Microsoft Support to determine if your environment would benefit from a change to this setting.
Making the change (only for documentation, it is already set to ON)
If you have consulted Microsoft Support, validated and considered the above points and fully tested the setting, the change can be made to your Dynamics CRM database by following these steps:
ALTER DATABASE [CRMDatabaseName] SET READ_COMMITTED_SNAPSHOT ON
To validate that RCSI has been enabled for your CRM Organization database, execute the following query:
Select name 'DB Name', is_read_committed_snapshot_on 'RCSI' from sys.databases WITH(NOLOCK)
Find the CRM Organization Database that you enabled RCSI for, and there should be a 1 in the “RCSI” column of the query results.
NOTE: Exclusive database access is needed for the setting to take affect so it may be necessary to stop services that are connecting to the database (W3WP, Async, etc.)
To disable RCSI, run the following statement against the CRM Organization database(s):
ALTER DATABASE [CRMDatabaseName] SET READ_COMMITTED_SNAPSHOT OFF
To validate that RCSI has been disabled for your CRM Organization database, execute the following query:
Find the CRM Organization Database that you disabled RCSI for, and there should be a 0 in the “RCSI” column of the query results.
Walter Carlin - MBA, MCSE, MCSA, MCT, MCTS, MCPS, MBSS, MCITP, MS
Senior Customer Engineer - Dynamics 365 - Microsoft - Brazil
Business Applications communities