deadlocks- details please

  • i know there are many posts on this forum regarding deadlocks..i did read through them but still have few questions...i would appreciate is someone can give a sql example of give an example off "AdventureWorks" dbs so that i can also test it...from what i understand..if there is an update going on a table and then there is another process trying to access that table...then it is deadlocked since update would put a lock on the table and the process doing select is aborted....then shouldn't this be blocking? i would appreciate if someone could explain me in detail..thanks in advance..

  • Here is a link that provies detailed explanations and examples.

    http://support.microsoft.com/kb/169960

    Dan

    If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.

  • What you described is blocking. Deadlocks occur when two processes attempt to generate locks on resources that the other process has locks on, usually in opposite order, so session_id =1 goes after TableA then TableB while session_id=2 goes after TableB then TableA. Neither session can release the lock it had on the first table and neither session can get the lock it needs on the second table.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • thanks

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

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