Post reply

"DEADLOCK PROBLEM"

  • January 25, 2010 at 1:14 am

    #138403

    Hi, I have bellow problem:

    I have two jobs, one is running continuously and the other is run every five minutes.

    Both load a temporal table which has the same name. The load is made the following way:

    insert #E

    select .....

    Then, a deadlock happen.

    How can happen if teporal tables belong a different jobs?.

    How can solve it?.

    Thanks.

  • January 25, 2010 at 3:06 am

    #1108053

    It happens because of different processes are waiting for same resource, in that scenario deda lock issue happens.

    SQL server has special mechanism which resolves the dead lock issue automatically by itself only.

    Thanks and Regards!!

    Thank You.

    Regards,
    Raghavender Chavva

  • January 25, 2010 at 3:08 am

    #1108054

    Switch traceflag 1222 on. That will result in a deadlock graph been written to the error log every time a deadlock occurs. Post the result of that graph here.

    DBCC TRACEON(1222,-1)

    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 25, 2010 at 3:12 am

    #1108058

    Raghavender (1/25/2010)

    SQL server has special mechanism which resolves the dead lock issue automatically by itself only.

    It does, but that doesn't mean that the root cause should not be fixed.

    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

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

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