Should I go for concurrency handling?

Question

1.00/5 (1 vote)

See more:

Hi,

I am working in a project related to Insurance and Finance domain. It is a web based application based on EDMX. The platforms which we are using ASP.NET 4.5 and Sql Server 2008. We have many screens and there are lots of places from where duplicate records can get saved. We have put unique non-cluster indexes in database tables but not doing any concurrency handling explicitly.

I am not sure about the reason that why our technical directors has not implemented concurrency handling but I guess might be because of performance issues. We have lots of tables and there are lots of inserts, updates, deletes used to fire.

So is it like if we are doing concurrency handling explicitly, then we may face serious performance issues?

Thank you.

Regards,
Nivedita

Posted 24-Jul-14 3:48am

Mukherji Nivedita

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)

Wendelius · Answer 1 · 2014-07-24T04:00:00

If concurrency handling is done properly, I believe you won't be facing any performance problems.

The key thing in my opinion is to use optimistic concurrency handling instead of locking for longer periods of time. The technique for this is to use rowwversions.

For starters, have a look at for example Data versioning in SQL Server using row versions[^].

Also introducing RVV like identifier in the updating DML statements you can easily spot potential lost updates. This is something that won't be handled by unique constraints and locks when updates are sequential :)

Mukherji Nivedita · Answer 2 · 2014-07-26T17:25:00

Solution 2

Thanks for the response Mika... I would definitely dig more into your suggestion !!

Posted 26-Jul-14 17:25pm