MSSQL Update Conflict

When a transaction running under snapshot isolation reads data that is then modified by another transaction, an update by the snapshot transaction to the same data causes an update conflict and the transaction terminates and rolls back. This is not an issue with
read committed isolation using row versioning.

Leave a Reply

Your email address will not be published. Required fields are marked *