Handling Concurrent user issue.

Question

3.00/5 (1 vote)

See more:

Hi,

I am using asp.net with SQL2008 facing a concurrent user issue, if two users launches the application and clicks save then it is allowing to save the record twice. I need to avoid saving duplicate record. How can I acheive this?

One thing I thought of taking Modifiedat value at the time of launching and comparing this value with database record if it differs then I will display message to the second user. Now the problem is we have migrated records which has same data of modifiedat.

Can any one let us know the best way to handle concurrency issue.
Your help is much appreciated.
-Mani

Posted 20-Dec-10 6:33am

techinical

Updated 20-Dec-10 7:01am

Slacker007

v2

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)

#realJSOP · Answer 1 · 2010-12-20T07:10:00

Two things you can consider:

0) You could lock the record being modified when someone requests the data, and then when a 2nd user requests it while the record is locked, make the edit fields read-only. Put a refresh button on the form and allow the user to re-request the data until he can put a lock on it himself.

1) When the user retrieves the data, save a copy of the data, allow the user to change it, and when he saves it, pass BOTH versions of the data to the database. If his copy of the original data is different than when is currently in the database, prompt him for further action.

Imran Saiyed · Answer 2 · 2010-12-20T07:22:00

Solution 2

Concurrent User Updates in ASP.NET and SQL Server[^]

Posted 20-Dec-10 7:22am

Imran Saiyed