Impact of installing/running SQL server profiler

https://msdn.microsoft.com/en-us/ms181091.aspx

Q1:
Is there any harm in installing the above & running it?  Will it chew a lot of resource and
amend something in the system (eg: registry keys or SQL tables / data structures) that
I can't reverse back cleanly?

Q2:
I'm troubleshooting something, so how do I run this profiler to capture a trace when
I'm reproducing the error?


We're on MS SQL 2008 Enterprise server running on Win 2008 R2 Ent  x64
sunhuxAsked:
Who is Participating?
 
Deepak ChauhanSQL Server DBACommented:
Q1. @Will it chew a lot of resource
      Yes, considerable server performance impact, You have to be more attention while running this, it will start capturing each and every event within a sever if filters are not applied correctly.

@ amend something in the system (eg: registry keys or SQL tables / data structures) that
     I can't reverse back cleanly?
 It is already installed with SQL server. you can open it from Tools tab in SSMS. it does not amend anything while running just capture the events and writing into the log files or log table.

Q2: I'm troubleshooting something, so how do I run this profiler to capture a trace when I'm reproducing the error?

You can open it from the Tools tab in SSMS menu and connect the database server for which you want to run the trace. select the event which you want to capture.

But try to not run it on production server run it remotely if possible.
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
We're on MS SQL 2008 Enterprise server
Extend Events are available since that version and it replaces SQL Trace and it's a much light process so you should use it instead of SQL Profiler.
0
 
sunhuxAuthor Commented:
> Extend Events are available since that version
So how do I run the above?  Is DBA privilege to DB required?
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Vitor MontalvãoMSSQL Senior EngineerCommented:
So how do I run the above?
Check the MSDN article. It explains how to use it and with examples.

Is DBA privilege to DB required?
No. Only requires the CONTROL SERVER permission for the instance of the SQL Server you want to use.
0
 
sunhuxAuthor Commented:
>try to not run it on production server run it remotely
How exactly is the above "remote run" done?  Can elaborate?
0
 
Deepak ChauhanSQL Server DBACommented:
remote run means you can open SQL profiler from any other client system and connect this server.  Since this is a production server and Profiler start using the resource utilization like CPU  and start writing the logs into file.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.