Posted by bjornsuneandersen on 07/06/07 22:12
I have a Stored Procedure that performs a simple SELECT. The Select
have no locking hints or other hints and the database is set up in a
standard configuration.
The problem is that the SELECT runs for some time and while it is
running I can see (in the profiler) that other SPs with simple SELECTs
are held waiting until "my" SP has finished. The other SPs may be
other instances of the same SP as the one I'm running. All SPs
contains simple SELECTs and should only hold shared locks.
I have also checked if there are any locks holding the other SPs back
- there isn't any.
So my question is: What resouce can hold out other simple SELECTs in
this situation? Where should I look to identify the resource?
Regards
Bjørn
Navigation:
[Reply to this message]
|