February 4, 2010 at 7:21 pm
Our developers wrote a stored proc that works fine when run from Query Analyzer but locks a table, the same table everytime, when run from either the VS.NET IDE or from an application. I can see which table is locked using profiler but I can't find what's causing the lock.
Any idea how to track down the source of this problem much appreciated? (Maybe I'm using the wrong counters in PerfMon?)
TIA,
Barkingdog
February 5, 2010 at 3:32 am
Barkingdog (2/4/2010)
Our developers wrote a stored proc that works fine when run from Query Analyzer but locks a table, the same table everytime, when run from either the VS.NET IDE or from an application. I can see which table is locked using profiler but I can't find what's causing the lock.Any idea how to track down the source of this problem much appreciated? (Maybe I'm using the wrong counters in PerfMon?)
TIA,
Barkingdog
Check the ISOLATION LEVEL.
VS.NET/Appliation is using SERIALIZABLE by default?
It is READCOMMITTED in QA/SSMS by default.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply