InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 05:36:23 GMT20http://www.sqlservercentral.com/Forums/Topic791038-146-1.aspxIt's a very good idea to turn on TRACEFLAG 1222. It can be difficult to interpret, but at least you're assured of capturing the information as each deadlock occurs. Otherwise, in order to capture the information, you'll need to run a trace 24/7. This can be a bit of a pain to maintain.To set the traceflag on:[code]DBCC TRACEON (1222,-1);[/code]Mon, 21 Sep 2009 06:35:13 GMTGrant Fritcheyhttp://www.sqlservercentral.com/Forums/Topic791038-146-1.aspx[quote][b]Sergey Vavinskiy (9/21/2009)[/b][hr]Here are a couple a good strategies:[url]http://weblogs.sqlteam.com/mladenp/archive/2008/05/21/SQL-Server-2005-Immediate-Deadlock-notifications.aspx[/url][url]http://www.mssqltips.com/tip.asp?tip=1036[/url][/quote]You can choose, do you want to know the process, or just catch it to investigte?1. Traceon can cath your deadock info so you can investigate and maybe correct some bad coding.2. get te SPID of the blocking process, and use it in DBCC INPUTBUFFER(spidid in here)example:DBCC INUTBUFFER(234)Result will show the query running/was running..Mon, 21 Sep 2009 06:30:13 GMTHenrico Bekkerhttp://www.sqlservercentral.com/Forums/Topic791038-146-1.aspxHere are a couple a good strategies:[url]http://weblogs.sqlteam.com/mladenp/archive/2008/05/21/SQL-Server-2005-Immediate-Deadlock-notifications.aspx[/url][url]http://www.mssqltips.com/tip.asp?tip=1036[/url]Mon, 21 Sep 2009 06:05:23 GMTSergey Vavinskiyhttp://www.sqlservercentral.com/Forums/Topic791038-146-1.aspxhow to findout the deadlock happend?how to resolve it?Mon, 21 Sep 2009 05:39:23 GMTcharipg