What's the difference between SQL Trace and the Profiler? When does it make sense to use one over the other?
Profiler is a client application where the SQLTrace or Server Side Traces are invoked through calling stored procedures on the server.
In general terms, I would use Profiler when trouble shooting a performance problem as it's occurring. I would use Server side traces for monitoring a production server....
The biggest reason that I thought for using a server side trace over Profiler was the band width usage in sending the results back to the client, but the following blog on SQLServerPedia, also points out that Profiler or client side traces can impact transaction throughput by as much as 10%
Also MSSQLTIPS has a good description for setting up server side traces: http://www.mssqltips.com/tip.asp?tip=1035
Steve: what kind of triky question is this? Isn't Profiler the tool used to start SQL Traces? So, basicaly, both are the same. You can´t choose one or another.
No one has followed this question yet.