|
For reading dirty data you can set isolation levels at a Connection level using
Do any of these help with locking / blocking issues at a global level?
or
(comments are locked)
|
|
I added tags for transaction and isolation-level to your question. There are some good answers in some of the previous questions: Which row-versioning transaction isolation level do you use? Transaction Types in SQL Server 2005 short answer: Yes, both help by reducing the need for locking but both also increase usage of tempdb. Just to clarify, those options are not for dirty reads. They are used to avoid lock/block issues when dirty reads are unacceptable.
Nov 18 '09 at 02:40 PM
Tom Staab
Good answer as usual, sir.
Nov 18 '09 at 04:27 PM
Matt Whitfield ♦♦
(comments are locked)
|

