Discussion Board

Dirty reads Dirty reads occur when a transaction reads data that has been written by another transaction that has not yet been committed. Dirty reads are only possible at the Read Uncommitted isolation level; however, the Serializable isolation level is sufficient to prevent dirty reads. At the Oracle default level of Read Committed, dirty reads are not possible. Prajakta Pandit 03-9-2017 12:26 AM

Dirty read Dirty reads occur when a transaction reads data that has been written by another transaction that has not yet been committed. Dirty reads are only possible at the Read Uncommitted isolation level; however, the Serializable isolation level is sufficient to prevent dirty reads. At the Oracle default level of Read Committed, dirty reads are not possible. Prajakta Pandit 03-9-2017 12:26 AM

Dirty Read A dirty read occurs when the first transaction reads uncommitted changes made by a second transaction. If the second transaction is rolled back, the data read by the first transaction becomes invalid because the rollback undoes the changes. Dirty Read 05-12-2015 12:24 AM

Wrong answer The answer given is wrong, infact Read Committed , Repeatable Read and Serializable will prevent dirty read. Dirty read occurs when you put (nolock) in your query. Anu 05-11-2015 04:46 PM

Write your comments

*

* Email must be in the form someone@domain.com

*

*