<div>
Yes. This article shows how to log for both errors and procedure usage:<br />
<br />
<a href="http://www.mssqltips.com/sqlservertip/2003/simple-process-to-track-and-log-sql-server-stored-procedure-use/" rel="ugc">http://www.mssqltips.com/sqlservertip/2003/simple-process-to-track-and-log-sql-server-stored-procedure-use/</a><br />
<br />
Or you could roll your own based on this approach to just trap and log the deadlocks.
</div>


Yes. This article shows how to log for both errors and procedure usage:

http://www.mssqltips.com/sqlservertip/2003/simple-process-to-track-and-log-sql-server-stored-procedure-use/ [http://www.mssqltips.com/sqlservertip/2003/simple-process-to-track-and-log-sql-server-stored-procedure-use/]

Or you could roll your own based on this approach to just trap and log the deadlocks.

<div>
<div class="content wysiwyg-content">
Hi <br />
<br />
is there any way &nbsp;to capture deadlocks in sqlserver 2005/2008 without using sql server profiler?<br />
<br />
Thx<br />
Naren
</div>
</div>


Hi 

is there any way  to capture deadlocks in sqlserver 2005/2008 without using sql server profiler?

Thx
Naren

Capturing deadlocks in Sqlserver 2005 and 2008 version

Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the  Always On technologies and support for unstructured data types.