The prob with read committed snapshot, is that if you turn it on, you are automatically turning off read committed, which is the default behavior. This means that all transactions where you do not specify an isolation level will use this, thus killing your server. That is why it is deprecated and removed in 2008...
Instead, I suggest that you use a locking hint, to force row locks, rather than table lock. This will not perform aswell, but will reduce the contention. Alternativly, just select a lower isolation level for the transaction. Make sure it is not set at a higher level than read committed (unless there is a compelling reason)
Main Topics
Browse All Topics





by: EndelmPosted on 2009-10-30 at 07:03:34ID: 25703028
While both of these new isolation levels have pros and cons, READ_COMMITTED_SNAPSHOT is generally recommended over ALLOW_SNAPSHOT_ISOLATION for the following reasons:
ormance.co m/articles /per/ new_i solation_l evels_p2.a spx
* It uses less tempdb space.
* It works with distributed transactions.
* It works with most pre-existing applications.
* It is not vulnerable to update conflicts.
http://www.sql-server-perf
U agree?