Search code examples
performancesql-server-2008deadlocksql-server-profiler

SQL Server Profiler issue

I am using SQL Server 2008 Enterprise and I want to use SQL Server profiler to capture deadlock event only. And when deadlock occurs and event captured, I will stop SQL Server profiler.

My question is, since I launched SQL Server profiler, and before deadlock occur (event captured), any impact (more about performance impact) to database?

thanks in advance, George

Solution

  • SQL profiler is another client of the database so it will impose some load, but quite little.

    You can see how much CPU etc is used by looking as sys.sysprocesses for the SPID used by profiler.

    However, you can also trap deadlock information to the SQL Server error log by using trace flags 1204 and 1222. And this link too for an overview.