http://sqlblog.com/blogs/linchi_shea/archive/tags/Deadlock/default.aspxTags: DeadlockenCommunityServer 2.1 SP2 (Build: 61129.1)http://sqlblog.com/blogs/linchi_shea/archive/2011/10/02/multi-victim-deadlocks-a-simple-example.aspxSun, 02 Oct 2011 05:33:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:38815Linchi Shea3http://sqlblog.com/blogs/linchi_shea/comments/38815.aspxhttp://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=38815Recently, I ran into a series of deadlocks that had multiple victims in each deadlock. In other words, SQL Server chose more than one spid to terminate in resolving a deadlock. Maybe I need to brush up my web search skills, but I have not found much information...(<a href="http://sqlblog.com/blogs/linchi_shea/archive/2011/10/02/multi-victim-deadlocks-a-simple-example.aspx">read more</a>)<img src="http://sqlblog.com/aggbug.aspx?PostID=38815" width="1" height="1">Deadlockmulti-victim deadlockshttp://sqlblog.com/blogs/linchi_shea/archive/2010/11/17/logging-for-post-processing.aspxWed, 17 Nov 2010 19:31:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:30685Linchi Shea3http://sqlblog.com/blogs/linchi_shea/comments/30685.aspxhttp://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=30685As a practicing database professional, I'm sure you have done a lot of logging, I mean, output and/or error logging from your scripts, your scheduled jobs, and any other programs you might have written. The primary purpose of logging, of course, is to...(<a href="http://sqlblog.com/blogs/linchi_shea/archive/2010/11/17/logging-for-post-processing.aspx">read more</a>)<img src="http://sqlblog.com/aggbug.aspx?PostID=30685" width="1" height="1">ScriptingAutomationDeadlock