README.txt describes how to update the
to support the version of SMO you have installed. It’s very easy to do.
This build supports SQL Server 2017, SQL Server 2016, SQL Server 2014, SQL Server 2012, SQL Server 2008 R2, and SQL Server 2008.
The new ClearTrace support forums are available at https://forums.sqlteam.com/c/cleartrace. If you have any issues please report them there.
The SMO libraries are now loaded using the partial name. This means that ClearTrace should “just work” with future versions of SQL Server.
The parsing is improved for SQL that looks like:
EXEC sp_executesql @statement=N’SELECT 1'.
(Introduced in Build 50)
There’s a new sort choice of “CPU & Reads”. This ranks each statement (or any item you’ve grouped by) on CPU and Reads. It then sorts based on the sum of the rankings. This should bring more interesting statements to the top. This was introduced in Build 50 but improved in Build 51.
This download contains the GUI and command-line versions. There is no installer. It will not create Start Menu entries or check for updates. The command-line version is still in beta. Please note that only the GUI version can create the database to store the results.
These are previous versions of ClearTrace. You should only use one of these if you need to read trace files generated on SQL Server 2000 or earlier.
This build supports SQL Server 2014, SQL Server 2012, SQL Server 2008 R2, and SQL Server 2008.
The new ClearTrace support forums are available at https://forums.sqlteam.com/c/cleartrace.
There is a check box to to skip importing traces files that are already imported. This is helpful if your trace script generates unique file names and you want to process a few traces files before the entire trace is completed.
There is logic to track prepared SQL. It tries to capture the prepare statement and then match up the executions to the prepare. It wasn’t capturing unprepare statements properly so it was filling up memory. It now clears the prepared SQL buffer after each file. This uses less memory and doesn’t crash. The downside is you’ll see a few more sp_executes with numbers.
The trace group filter name is now much wider.
Viewing the detail for statements also shows the history. Previously the history was combining batches and statements. Or just plain throwing an exception. It works and show the proper results.