Automatically Processing SQL Server Trace Files

Lately I've been working on a small utility to process SQL Server trace files.  If you use scripted traces to generate trace files there's no automated way to get these into a SQL Server table.  I wrote a little .NET utility to do it for me that I'm calling ClearTrace.  You can download it here.  Currently it's a command line utility and VERY beta.  In the future I plan to rewrite it as a service and add better error checking. 

ClearTrace should run on an admin workstation and not on the server.  It watches trace files based on a filter you specify.  It's best to share out the directory where your trace files are stored.  After each trace file is completed and the system rolls over to the next trace file, ClearTrace will process the trace.  It will be moved to a working directory and renamed with a time stamp appended to the file name.  ClearTrace will then load the trace file into a specified table on a specified server.  If the table doesn't exists, ClearTrace will create it for you.  It can handle an unlimited number of traces each going to its own SQL Server and table.  After the trace file is loaded, ClearTrace will move the file to an archive directory.  Each trace can specify its own working and archive directories.  Each trace can also specify how long to retain the archived trace files before they're deleted.

If you find any problems, please let me know.  I'd also be interested in feedback on whether this is a usefull application or not.  At this point the source code isn't available but I may make it available in the future.

Show Comments