Post reply

Deadlock at primarykey column

  • January 18, 2011 at 10:50 pm

    #1275101

    kthanigaivel (1/18/2011)

    sorroy that table contains 50 thousand rows.

    Still a pretty small table, especially if you mean 50 000 rows = 4.5MB. My answer stands as is.

    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

  • January 21, 2011 at 12:17 am

    #1276397

    Update Trn_GJobDet set CompletedDate=getdate() , CompletedEmpId=4335

    Where QueueId < 2 and JobCardId=116111 and StageId=53 and

    SubJobId=971218 and CompletedDate is Null and IsActive=1

    If this table contains only 50 rows i dont think the table scan hurts performance and lead to a dead lock.

    We really need to understand what triggers this update statement.

    Probably some transaction holds the lock of this table and it is not commited and this update statement triggered leads to the dead lock.

    Please analyze more what triggers this update statement.

Viewing 2 posts - 16 through 16 (of 16 total)

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