Remote profiling

I keep reading how you are supposed to run traces from a remote server, but I
don't see any way to do that using sp_trace_create. Can this only be done by
running SQL Profiler from the remove server?
Thanks,
Brandon
Where do you see this advice and what exactly do you mean by "run traces
from a remote server"? sp_trace_create like any sp will be run on the
server you are connected to regardless of where the client app is that
issued the statement. The preferred way to create the trace is to have it
output directly to a file on a locally attached drive (not a network share).
It does not matter where you start the trace from just where the file will
be. If you run Profiler this is different. It is a client app but requires
the trace information be sent back to the client for display and processing.
This can be very expensive in some cases and should only be used on light
loads or small periods of time. You can always take the file produced from
sp_trace_create and load it into profiler anywhere you like with no impact
on the server other than what it takes to copy the file to the client.
Andrew J. Kelly SQL MVP
"Brandon Lilly" <avarice@.nospam_swbell.net> wrote in message
news:AF8A2C1F-75AB-4F30-8951-433BB13EA988@.microsoft.com...
>I keep reading how you are supposed to run traces from a remote server, but
>I
> don't see any way to do that using sp_trace_create. Can this only be done
> by
> running SQL Profiler from the remove server?
> Thanks,
> Brandon
|||Is it possible to load the profiler client app on a system running SQL 2005
Express?
Thanks
Clyde
"Andrew J. Kelly" wrote:

> Where do you see this advice and what exactly do you mean by "run traces
> from a remote server"? sp_trace_create like any sp will be run on the
> server you are connected to regardless of where the client app is that
> issued the statement. The preferred way to create the trace is to have it
> output directly to a file on a locally attached drive (not a network share).
> It does not matter where you start the trace from just where the file will
> be. If you run Profiler this is different. It is a client app but requires
> the trace information be sent back to the client for display and processing.
> This can be very expensive in some cases and should only be used on light
> loads or small periods of time. You can always take the file produced from
> sp_trace_create and load it into profiler anywhere you like with no impact
> on the server other than what it takes to copy the file to the client.
> --
> Andrew J. Kelly SQL MVP
>
> "Brandon Lilly" <avarice@.nospam_swbell.net> wrote in message
> news:AF8A2C1F-75AB-4F30-8951-433BB13EA988@.microsoft.com...
>
>