Post reply

Deadlock Information in Profiler (ObjectID2 way too large)

  • November 13, 2009 at 5:43 pm

    #212291

    I'm trying to diagnose a deadlock issue with our application in SQL 2005. In Profiler, I'm capturing EventClass "Lock:Deadlock", and "Lock:Deadlock Chain". For each instance captured I get a 0 for ObjectID, and a huge number (300259171368960) for ObjectID2. That number is much larger than any ID in sys.sysobjects (max id is 2146926820). I know I'm missing something, but not sure what it is.

    Any help is greatly appreciated.

  • November 14, 2009 at 2:27 am

    #1079342

    It's not an objectid, it's a partitionid. Query sys.partitions to get the objectid and indexid

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • November 16, 2009 at 8:48 am

    #1079714

    Thank you, thank you, thank you! Now off to battle the deadlock issue.

  • November 16, 2009 at 8:57 am

    #1079731

    If you need some help with that, start a new thread and post (or attach) the deadlock graph, along with definitions of the tables involved.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • November 16, 2009 at 10:17 am

    #1079786

    I will certainly do that if the need arises. I need to sit with the developers first and figure out what's going on with the code. I'm running another trace now to capture the deadlock graph, which I neglected to do the first time.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply