Restrict simulteneous acces of stored procedure

Question

0.00/5 (No votes)

See more:

I have a stored procedure as follow:

SQL

insert into callbook
(
callsrno,calldate,customerid,product,modelid,srnumber
,purdate,warranty,dealerid,complaint,enqtype,callfrom
,prefdate,preftime,callstatus,ipaddr1,userid
)
 values 
(
convert(nvarchar(11),@callsrno),@calldate ,@customerid ,@product ,@modelid  ,@srnumber ,
@purdate,@warranty ,@dealerid  ,@complaint,@enqtype ,@callfrom ,
@prefdate,@preftime ,@callstatus ,@ipaddr1 ,@userid 
)

But some time more than one user accessed this sp.
and ambiguous record saved in my database.

So I want to restrict simultaneous access of SP.

Thnx...

Posted 7-Aug-12 22:35pm

Kailash_Singh

Updated 7-Aug-12 23:24pm

Prasad_Kulkarni

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)

Philip Stuyck · Answer 1 · 2012-08-07T23:22:00

What do you mean by ambiguous record ?
I think you just need to implement referential contraints: for instance unique index constraints to protect your data from getting corrupted.
Because you are doing an insert the record itself that is being inserted cannot get corrupted, the only possibility I see is that it might be inserted twice if you do not have the proper referential constraints.

skydger · Answer 2 · 2012-09-17T08:36:00

Solution 2

If you use MS SQL Server 2005 or higher you can use table hints such as locks (exclusive - TABLOCKX, or simple TABLOCK) to prevent simultaneous insert's in it.
http://msdn.microsoft.com/en-us/library/ms187373.aspx[^]

Posted 17-Sep-12 8:36am

skydger