So, I have some deadlocking issues.
I have seen two options to resolve it. Add
read uncommitted to my db or do Snapshot Isolation and add
read committed snapshot.
After doing some research into both, it seems to me that
read uncommitted can allow reads of data that could possibly never get committed to the database.
On the flip side
read committed snapshot will give only the latest (it is the latest right?) committed version of data (even if the data that may be in the middle of a change/transaction.)
Is this right?
If so, I am leaning towards Snapshot Isolation (I don't really want to return data that is in the middle of a change.)
However, my DBA told me that last he heard there were "problems" with Snapshot Isolation. (He did not expand on the the problems were, just that it was not a Enterprise ready feature.)
So, here are my questions on Snapshot Isolation:
Is Snapshot Isolation robust? Does it just work?
Or are there "gotchas" that I need to look out for?