Skip to main content

Minimize Deadlocks Between Read and Write Operations

Elizabeth Warden
  • Updated

Issue

By default, the Is Read Committed Snapshot On and the Allow Snapshot Isolation SQL Server database settings are set to disabled. In the delivered application databases, certain activities could result in deadlocks under heavy volume.

Solution

Enable the Is Read Committed Snapshot On and the Allow Snapshot Isolation database settings. These options set the database engine to use row versioning and snapshot isolation as the default.

The following is a screenshot of where the Is Read Committed Snapshot On and Allow Snapshot Isolation are located in the Model database settings:

MinDeadlocks.png

Syniti has different recommendations for this setting in Migration versus Governance applications:

  • Migration—this setting is not recommended as a general setting for Migration applications because it does result in some performance issues.
  • Governance—this setting is recommended for Governance applications to help with potential deadlock issues.

Refer to Snapshot Isolation in SQL Server to learn more about this setting. 

Related articles