Lock a Sql Server Table While Read

Question

1.00/5 (1 vote)

See more:

I am working on a winform application where on a butoon click in a form, I have to first read the Sample table values billNo abd kotNo and then increment those values(in a single stored procedure). But the problem area is that any other user can also read the same value simultaneously, and increment those values. so resulting in two biils having same billno.

SQL

CREATE TABLE [dbo].[Sample](
    [billNo] [decimal](6, 0) NOT NULL,
    [kotNo] [decimal](6, 0) NOT NULL,
    [initials] [char](3) NOT NULL,
    [unit_code] [char](3) NOT NULL
)

please help me to rectify my problem.

regards
Vijay

Posted 3-Jan-12 18:33pm

vijay tkakur progchd

Updated 3-Jan-12 19:11pm

Wendelius

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)

2irfanshaikh · Answer 1 · 2012-01-03T18:50:00

Solution 1

I think this link will help you

Click Me[^]

Posted 3-Jan-12 18:50pm

2irfanshaikh

Wendelius · Answer 2 · 2012-01-03T19:19:00

First of all you should have a transaction if not already present. See: BEGIN TRANSACTION[^]

Now if this is the same table you're reading and updating, why not use a single update statement. Something like:

SQL

UPDATE MyTable
SET COL = COl + 1
WHERE ...

However, I would not store calculations in a table so consider redesigning the application to fetch the amount you're interested in at runtime. This would prevent extra logic and ensure that you always get correct results.