July 10, 2012 at 7:57 am
Hi Guys,
I am running an application where there is happening insertion and updation with select by cuncurrntly different users,So the table level lock is happening after some time the none of the user is allowed to log in and the select suspension is happening and the table level lock.
can any one suggest what should be our approach or Do we need to disable the table level locking ..
Please suggest.
Thanks,
Prafull
July 10, 2012 at 8:11 am
What version of SQL Server are you running, and also what isolation level is it running at? If you're on 2005 or higher consider moving to Read Committed Snapshot isolation. That would allow you to accomplish what you're looking for where readers don't block writers and vice versa.
July 10, 2012 at 1:12 pm
Proper indexes can also help with this issue as you can get more granular locking which increases concurrency.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply