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?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.