Non Repeatable Read-SQL Server-Concurrency problem


Non Repeatable Read is also one of the concurrency problem in SQL Server. And it also causes confusion when two or more user working/reading on the same data.

Let see the situation, how problem occurs?
When one transaction reads the same data twice and another transaction updates that data in …

SQL Server-Common Concurrency Problem


Problem Everywhere.. Solution Everywhere..

If two or more transaction is accessing the same resource at same time. There is a problem of concurrency. Lets discuss what are the common problem arises in SQL Server.
1) Dirty Read
2) Lost Update
3) Non-repeatable Reads
4) Phantom Reads

Common Concurrency Problem | Lost update | Academy4Code.com
Common Concurrency Problem |

Isolation level-ReadUnCommitted: Pictorial Representation -Phase#2


Here is the pictorial representation to show , how the dirty read occurs in the system. This is mainly occurs when we set the Isolation level from Read Committed to Read UnCommitted(NoLock). There is no difference between Nolock and Read UnCommitted in SQL Server.

Before reading this, you must …