Profiler always doing something

New to SQL Server.
How can I determine how much the Profiler is dragging down a server? I am
running a trace from my pc against a database server but I wish there was a
before and after report that would show how much the Profiler drags down a
server. I am also stroring the trace here on my pc.
I generally prefer to use a server side trace rather than using the Profiler
GUI for anything but short term troubleshooting to minimise the impact, also
be very specific about what events you are monitoring. In terms of imapct,
you would need to use perfmon to measure it but would obviously need to
capture stats before starting the trace as a baseline to compare to when
Profiler is running. For tips on using Profiler/Trace have a look at
http://www.sql-server-performance.co...filer_tips.asp
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:B1302B2C-0292-462F-96AF-E2D3D1CFD49F@.microsoft.com...
> New to SQL Server.
> How can I determine how much the Profiler is dragging down a server? I am
> running a trace from my pc against a database server but I wish there was
> a
> before and after report that would show how much the Profiler drags down a
> server. I am also stroring the trace here on my pc.
|||Hello Jasper,
I got that server side down! I am using SP to capture my stats. I guess
you are right, use Perfmon first to get a baseline then run the SP to see how
hard to drives the server.
"Jasper Smith" wrote:

> I generally prefer to use a server side trace rather than using the Profiler
> GUI for anything but short term troubleshooting to minimise the impact, also
> be very specific about what events you are monitoring. In terms of imapct,
> you would need to use perfmon to measure it but would obviously need to
> capture stats before starting the trace as a baseline to compare to when
> Profiler is running. For tips on using Profiler/Trace have a look at
> http://www.sql-server-performance.co...filer_tips.asp
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:B1302B2C-0292-462F-96AF-E2D3D1CFD49F@.microsoft.com...
>
>
|||Just to add to this:
The overhead that Trace imposes on a server depends very much on what events
and columns you selected for tracing and how often those events occur. So it
is difficult to give any single number, the best way is to measure yourself.
Regards,
Maciek Sarnowicz
SQL Server Tools SDE
This posting is provided "AS IS" with no warranties, and confers no rights
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:A88E6302-3DDE-4C16-B247-2CE9E377A550@.microsoft.com...[vbcol=seagreen]
> Hello Jasper,
> I got that server side down! I am using SP to capture my stats. I guess
> you are right, use Perfmon first to get a baseline then run the SP to see
> how
> hard to drives the server.
> "Jasper Smith" wrote:
|||Thanks Maciek,
I have the hang of making the trace into a stored procedure and letting the
SQL Agent call it as a job. I just do not want to "give" the SQL Agent the
permission to start a trace and then the trace slows the database server way
down. This could happen if the volume goes up on the server. I may need to
have a Alert set to Knock off the job if it becomes too busy...
"Maciek Sarnowicz [MSFT]" wrote:

> Just to add to this:
> The overhead that Trace imposes on a server depends very much on what events
> and columns you selected for tracing and how often those events occur. So it
> is difficult to give any single number, the best way is to measure yourself.
> Regards,
> Maciek Sarnowicz
> --
> SQL Server Tools SDE
> This posting is provided "AS IS" with no warranties, and confers no rights
>
>
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:A88E6302-3DDE-4C16-B247-2CE9E377A550@.microsoft.com...
>
>
|||Rich wrote:
> Hello Jasper,
> I got that server side down! I am using SP to capture my stats. I
> guess you are right, use Perfmon first to get a baseline then run the
> SP to see how hard to drives the server.
>
Profiler has a lot of overhead compared to using a server-side trace.
Server-side traces are quite efficient and generally pose little impact
on servers. And just so you know, running a server-side trace from the
Profiler client actually creates and runs two traces on the server: a
server-side and a normal Profiler trace.
David Gugick
Imceda Software
www.imceda.com