best isolation level to use in sql transaction

Question

0.00/5 (No votes)

See more:

hi friends
designing an accounting software using c# winform . so here is a case that requires me to insert into one table and update another table say deduct 10 from accountA and update accountB .i know i have to use transaction but my problem now is choosing the type of isolation i should use,or should i just use the default isolation level
thanks in advance...

Posted 4-Jul-14 3:02am

Ese Ochuko

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

PIEBALDconsult · Answer 1 · 2014-07-04T03:21:00

Solution 1

I'd stick with the default. And most people would do that in a stored procedure.

Posted 4-Jul-14 3:21am

PIEBALDconsult

Comments

Richard Deeming 4-Jul-14 9:35am

The default isolation level is "Read Committed". That can give you both phantom reads and non-repeatable reads, which wouldn't be acceptable for a transaction moving money between accounts.

Richard Deeming · Answer 2 · 2014-07-04T03:21:00

For accounting solutions, I'd be inclined to use SERIALIZABLE. All other levels could potentially lead to problems.

Isolation Levels in the Database Engine[^]

SNAPSHOT might seem tempting, but it has numerous problems for this type of application:
The SNAPSHOT Isolation Level[^]

SQL Server 2005 Row Versioning-Based Transaction Isolation : Understanding Isolation[^]