About SQL Server Row Versioning
The SQL Server Database Engine supports an optimistic concurrency control mechanism (versus pessimistic concurrency) based on row versioning. Learn more.
Read MoreMost Popular Concurrency
When You Might See SQL Server Concurrency Problems
If SQL Server locking isn’t used, and no isolation exists between transactions, you may have concurrency problems such as lost updates, dirty reads, nonrepeatable reads and phantoms. Learn more.
Read MoreThe Nuts and Bolts of Locking in SQL Server 2012
Every DBMS has mechanisms that control the access of data by all users at the same time. The SQL Server Database Engine uses locks to guarantee the consistency of the database. Learn more.
Read MoreConcurrency Models in SQL Server 2012
The SQL Server Database Engine supports two different concurrency models: pessimistic concurrency and optimistic concurrency. Learn more.
Read MoreSQL Server Concurrency–Non-repeatable Reads
Nonrepeatable reads can happen when multiple sessions are occurring at once in your SQL Server database instance. Learn more.
Read MoreSQL Server Concurrency–Lost Updates
Database concurrency ensures that when multiple operations are occurring at once, the final result is still in agreement. Lost updates can happen when multiple sessions are occurring at once in your SQL Server database instance.
Read More