Deadlock errors result with high concurrency on SQL Server.
Symptoms
Database operations fail because of transaction deadlock
errors.
Causes
High concurrency blocks readers' access to database resources
by writers, resulting in deadlocks.
Resolving the problem
READ_COMMITTED_SNAPSHOT is required on SQL Server to reduce deadlocks.
To
enable Read-Committed Snapshot Isolation on
SQL Server:
- Shut down all of the servers and clients, and make sure there are no other connections to
SQL Server.
- Connect to SQL Server and
issue the following command:
ALTER DATABASE dbName SET READ_COMMITTED_SNAPSHOT ON
- Restart SQL Server and
verify that the Read-Committed Snapshot Isolation setting takes effect
for new connections.