Error!
Success!

SQL Server 2008 Concurrency Problems and Isolation

0
kicks

SQL Server 2008 Concurrency Problems and Isolation  (Unpublished)

Concurrency problems SQL Server transaction isolation solves four major concurrency problems Dirty read occur when a reader reads uncommitted data Unrepeatable read occurs when existing row change within a transaction Lost updates occur when two writers modify the same piece of state Phantoms occur when new rows are added and appear within a transaction Locking strategies Optimistic concurrency


Kicked By:
Drop Kicked By: