27 ms·
Since the transaction that did the write is uncommitted, dirty reads are generally a bad idea as you may act based on something that is subsequently thrown away
by Robin_Message 9y ago
Since the transaction that did the write is uncommitted, dirty reads are generally a bad idea as you may act based on something that is subsequently thrown away.
Only useful use I've found for them: emulating sequences on a DB without them.
- jonballant 9y agoThis is a good article that outlines some of the pros of the Read Uncommitted Level. When speed is pertinent and you need to run multiple transactions quickly, such as an E-commerce store, Read Uncommitted allows you to immediately execute the next transaction, without waiting for the first to complete execution. http://codingsight.com/understanding-dirty-read-problem-sql-server/ http://codingsight.com/understanding-dirty-read-problem-sql-...
- jonballant 9y agoCould another use be to debug something that is happening inside a transaction? https://stackoverflow.com/questions/2471055/why-use-a-read-uncommitted-isolation-level https://stackoverflow.com/questions/2471055/why-use-a-read-u...