Dynamics 365 Business Central: SQL Server and Read Committed Snapshot Isolation impact.
The latest release of Dynamics 365 Business Central introduced the TRI STATE LOCKING feature and the new READ COMMITTED transaction isolation level. Enabling the Tri-state locking feature on the SaaS version is simple, but for on-premises installations, you need to enable Read Committed Snapshot Isolation on SQL Server. This feature allows SQL Server to return the old committed record version from the Version Store instead of locking a record during a reading operation. However, enabling this feature can cause performance issues if there is no free space available on the data page. To optimize the SQL database, it is recommended to enable Read Committed Snapshot Isolation immediately when creating a new database or rebuild indexes and heap tables for existing databases. Overall, enabling Read Committed Snapshot Isolation can help reduce blocking situations and deadlocks in Dynamics 365 Business Central on-premises installations.
Article 17m
Login now to access my digest by 365.Training
Learn how my digest works
Features
- Articles, blogs, podcasts, training, and videos
- Quick read TL;DRs for each item
- Advanced filtering to prioritize what you care about
- Quick views to isolate what you are looking for right now
- Save your favorite items
- Share your favorites
- Snooze items you want to revisit when you have more time