I'm doing some research on database isolation levels and which allow dirty reads through isolation level READ UNCOMMITTED. The advantage seems to be speed and latency but at the cost of accuracy and consistency. My question for the community is if allowing Dirty Reads is preferred?
I'm certainly not the most knowledgeable in this at all, but if I'm not mistaken most environments I've worked in have been only the dev instance allows it, while UAT and production won't allow any dirty reads.
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.<p>Only useful use I've found for them: emulating sequences on a DB without them.