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.
| Author |
Topic |
|
Zoroaster
Aged Yak Warrior
702 Posts |
 Posted - 2007-10-17 : 18:26:33
|
When running a profiler trace for long running queries during peak usage what is a typically expected additional load the process of running it will create on that Database?
Future guru in the making. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-10-17 : 18:28:31
|
| I've seen SQL Profiler slow my mission critical production databases to a crawl. As a result of this, I did some researching and found that MS highly recommends that you save the trace results to a file rather than to a SQL table. This greatly improved performance for me. Now with the file, the resources needed to run a trace are negligible.And with the MS-provided function that allows you to read trace files just like it was a table, I never store my trace data in SQL tables.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
Zoroaster
Aged Yak Warrior
702 Posts |
Posted - 2007-10-17 : 18:32:48
|
Thanks - good information. I am actually planning to run profiler from another local server (test server) and save to a file on that server as well to reduce overhead.
Future guru in the making. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-10-17 : 18:38:12
|
| Yes that is what I do as well. Never, ever run the tool on the actual database server. Run it from a client machine and save the results to a file.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2007-10-18 : 03:26:43
|
| Also think about using only the events you require and filter as efficiently as possibleJack Vamvas--------------------Search IT jobs from multiple sources- http://www.ITjobfeed.com |
|
|
|
|
|
|
SQL Profiler