|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Saturday, February 09, 2013 3:44 PM
Points: 345,
Visits: 565
|
|
Hello Folks,
am in similar kind of situation, on one of my Production server there are so many lockings are there it is causing performance problem.
1)I run a query sp_who4 active it results in same query with same login but different SPID's are showing in command text column.
2) SPID is blocking by same SPID is more than once. i.e., ex: SPID:98 is BLKBy 98.
3) I run a SQL profiler and please guide me what to do next and how to fix this issue ASAP.
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Friday, August 31, 2012 7:19 AM
Points: 225,
Visits: 419
|
|
srinath.vanama (8/16/2011) Hello Folks,
am in similar kind of situation, on one of my Production server there are so many lockings are there it is causing performance problem.
1)I run a query sp_who4 active it results in same query with same login but different SPID's are showing in command text column.
2) SPID is blocking by same SPID is more than once. i.e., ex: SPID:98 is BLKBy 98.
3) I run a SQL profiler and please guide me what to do next and how to fix this issue ASAP.
Srinath... This is a year old thread...
See when you're seeing a spid blocking itself then this is not a blocking issue this is a common scenario in multiple core systems....
Can you confirm you SQL Server edition and sp level.
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Saturday, February 09, 2013 3:44 PM
Points: 345,
Visits: 565
|
|
Sql Server 2005 Enterprise edition and SP2.
If this is not a Blocking issue, what might be the problem and how to fix this issue.?
Kindly suggest me to fix this problem.
|
|
|
|
|
SSC-Insane
         
Group: General Forum Members
Last Login: Yesterday @ 2:27 PM
Points: 21,357,
Visits: 9,537
|
|
Medhatithi Guha (8/15/2011) Is this sql server 2005? Then run a profiler and capture the deadlock graph. Deadlock can occur because of a lot of reasons and the deadlock graph will give you a good idea where to start.
Also, just an observation. Most of the times while resolving deadlocks,we tend to look for X locks only. But please do examine the S locks also and let us just remember that a deadlock occurs on one (or more) resource. That resource can be a table itself, a row, a page, an index anything. Even a simple select and then and update statement may lead to a deadlock. So best idea would be to get hold of the deadlock graph first and then only can this problem be solved
Please start a new thread.
|
|
|
|