Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Effects of Profiler Trace on Server

Author  Topic 

techies
Starting Member

2 Posts

Posted - 2008-12-22 : 19:55:54
I want to run a trace on our servers for a while to get a large data sample... but I'm afraid of how taxing it is to keep it going for the servers. What's a rough estimate of performance loss due to the trace? (5%? 10%?) Relatively busy server during peak hours, constant activity 24/7.

dinakar
Master Smack Fu Yak Hacker

2507 Posts

Posted - 2008-12-22 : 20:24:24
hopefully you are running server side trace and not profiler? the only way to find out how much affect it will have is to actually run it. I would start at a non peak time and check the CPU.

Dinakar Nethi
************************
Life is short. Enjoy it.
************************
http://weblogs.sqlteam.com/dinakar/
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-12-22 : 22:53:16
SQL Profiler can bring the server to its knees. I've taken down production by tracing for too much information in SQL Profiler. It's much better to use a server-side trace. But if you must use SQL Profiler, follow this: http://weblogs.sqlteam.com/tarad/archive/2008/08/06/SQL-Profiler-best-practices.aspx

According to what I've read and heard, a server-side trace should have consume less than 5% of resources. But SQL Profiler, if configured poorly, can use a lot more than that.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -