Now, as for your exact problem, I suggest a multipart solution. You should set up the trace to have a maximum size, either its max size for the day or for the week. (You should have a pretty good idea how big the trace file will get.) Then set up a DTS job to do the following on either a daily or weekly schedule:
- Stop the original trace.
- Zip the file and copy it to an archival location.
- Start a new trace.
Also, please remember that SQL Profiler is generally used as a diagnostic tool and not a long-term monitoring tool. I suggest you consider other monitoring options for the long term.
Dig Deeper on Microsoft SQL Server Performance Monitoring and Tuning
Related Q&A from Kevin Kline
Monitoring and Administration expert Kevin Kline discusses the obstacles of database administration when a publisher resides on a different domain. Continue Reading
A common SQL Mail error is addressed by monitoring and administration expert Kevin Kline. Continue Reading
Monitoring and Administration expert Kevin Kline discusses the installation of SQL Server client tools on Windows XP Pro. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.