January 2, 2014 at 2:19 pm
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/[/url]
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?
Likes to play Chess
January 2, 2014 at 3:03 pm
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
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply