[dba-SQLServer] Trace kills performance?

IME it is often better to dump the results to a file especially on big and
busy servers.

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

> Yes, that is what I assumed, and how I set it up. One detail, however: I
> directed the trace results to a table rather than a file. Was that a bad
> idea?
>
> Thanks,
> Arthur
>
> On 7/10/08, Francisco Tapia <fhtapia at gmail.com> wrote:
> >
> > 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.
> >
> _______________________________________________
> 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...