SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Running Client-side Profiler trace or Server-side trace?


Running Client-side Profiler trace or Server-side trace?

Author
Message
VoldemarG
VoldemarG
SSC-Enthusiastic
SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)SSC-Enthusiastic (128 reputation)

Group: General Forum Members
Points: 128 Visits: 202
as some reference like this one suggests
http://support.microsoft.com/kb/929728 that SQL Server instance is affected considerably while client-side GUI-based trace is running. It points out that such adverse affect is observed using SQL 2000 or 2005.
Another article here http://www.sqlservercentral.com/articles/Performance+Tuning/71549/
suggests to run Server-side automated trace (not using Profiler GUI but T-SQL/Agent).

I plan to run trace capturing several SPs-related events only. But I want to run it for a couple of days in production server (one SQL server is 2008 and another 2012). In the first KB article that I mentioned above it says that such symptoms as noticeable server slowdown is applicable if it is version 2000 or 2005. Does anyone know if in versions 2008 and 2012 such concern has diminished?

Or is the same also true for versions 2008 and 2012 that I am going to run this long trace on, and should I then still consider server-side traces?


Voldemar
likes to play chess
Lowell
Lowell
One Orange Chip
One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)

Group: General Forum Members
Points: 28103 Visits: 39938
profiler is resource intensive, no matter the SQL version.
consider this:
there is nothing a slow, resource intensive profiler trace can do that a server side trace cannot do.

EVERY client side trace can be replaced with a low impact server side trace; there are no exceptions to that, because whatever you build as a client side trace can be scripted to be a server side trace template.


for me, running profiler is something i might do if i wanted to do a right now diagnostic, otherwise i'd build the template in profiler and save it as a script to create on the server.

Lowell

--
help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search