It is well known that
running a profiler consumes a lot of resources depending on what events are being monitored.
I am interested in monitoring deadlocks that occurs occasionally (3~5 a week).
using SQL Server profiler with following event selections (every event but highlighted ones from
Would it slow down to monitor(for one whole week without stopping) only locks against production databases?
Are there any rules of thumb on when and how long to run the profiler for deadlocks?