This post has been moved to my new blog at SQLBlog. You can find its contents on the following link:
http://sqlblog.com/blogs/jonathan_kehayias/archive/2008/11/25/anatomy-of-a-deadlock-part-deux.aspx
1 year ago
Tuesday, November 25, 2008
Subscribe to:
Post Comments (Atom)
Very smart and deep analysis!
ReplyDeleteThe graph and analysis shows how this interesting deadlock occur.
Thanks!
Very nice blog post! :)
ReplyDeleteHi Jonathan,
ReplyDeleteWhen I try to describle why occur deadlock when I changed the isolation level from "Serializable" to "ReadCommitted"(please note: the index is also a non-clustered index), I can't continue.
Because the deadlock chain show it is Page Block( the table, in the heap). Could you kindly explain for the type deadlock? Very thanks!
Regards
Hong Hai
Hi,
ReplyDeleteI have also posted into the MSDN forum, to refer to the deadlock chain xml code, your blog can't accept the xml tag.
http://forums.microsoft.com/msdn/showpost.aspx?postid=4172493&siteid=1&mode=1&sb=0&d=1&at=7&ft=11&tf=0&pageid=1
Thanks in advance!
Regards
Hong Hai
As posted back on that forums thread, the problem is still with this being a heap structure and most likely with forwarding records in the allocation units. Change it over to a clustered index and retest for deadlocking.
ReplyDelete