Transaction Isolation Level

The transaction isolation level is primarily used as a means to provide accurate and reliable access to data within concurrent transactions. For example, two different transactions might be accessing the same data simultaneously. Therefore, if the change made on the data by one transaction is not passed to the other transaction, it can affect database operations. To circumvent this, DBMS employs different transaction isolation levels that enforce read and write locks on the data. There are four different types of transaction isolation levels.

1. Serializable: Implements read and writes locks until the transaction is finished. Also implements range locks.
2. Repeatable Reads: Implements read and write locks until the transaction is completed. Doesn’t manage range locks.
3. Read Committed: Implements write locks until the transaction is completed but releases read locks when a SELECT operation is performed.
4. Read Uncommitted: One transaction can see the uncommitted changes made by the other transaction