Data source transaction isolation level descriptions

codevally May 29, 2012 2:57 AM

The available transaction isolation levels are (according to the documentation)

Could someone please explain what is suitable for what situation.

Thanks.

1. Re: Data source transaction isolation level descriptions

wdfink May 30, 2012 2:06 AM (in response to codevally)

Depends extreme on your requirements.
A description of the levels can be found at wikipedia
I think the most common is READ_COMMITED. If you don't want to overwrite changes you should use optimistic locking.

SERIALIZABLE is the highest level and it will be slow down the access because there is no concurrent access.
Actions
2. Re: Data source transaction isolation level descriptions

pradeepn Sep 10, 2013 6:31 AM (in response to codevally)

Checkout the link below, this might help you deciding on which one to use.
Chapter 5. Transactions and Concurrency
Actions