[dba-SQLServer] Trace kills performance?

Traces are generally expensive, performance exercises of patience, you
should run them while you are troubleshooting an issue in this case the
deadlock issue, but they will cause a performance drain on your system, how
much generally depends on where you are writing the trace file to, in
general you can get the slightly better performance by running the trace
from a remote client where you write the file to local storage.



On Thu, Jul 10, 2008 at 6:10 AM, Arthur Fuller <fuller.artful at gmail.com>
wrote:

> I was running a relatively simple trace using the locking issues template
> and I can't believe how much it killed the server performance. I'm new to
> tracing so maybe this is just how things are. I'm going to do another one
> soon, and narrow the focus just to deadlocks. Hopefully that won't cripple
> performance.
>
> Anyone got some insights about this?
>
> TIA,
> Arthur
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>


-- 
-Francisco
http://sqlthis.blogspot.com | Tsql and More...