What's new in ClearTrace Build 56
Sep 4, 2019
- This build doesn’t requires a specific version of SMO. The README.txt describes how to update the .config file to support the version of SMO you have installed. It’s very easy to do.
- This has been tested using the SMO libraries from SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.
- This build only reads extended event files. For trace files, please download the older version below.
- The File Select doesn’t support wildcards. Instead you can browse (open) the directory and select multiple files. This worked much better in my testing. It also doesn’t automatically process all files in order when you select the first one. You’ll need to select all the ones you want to process.
- The database format is the same as ClearTrace for Trace. Due to parsing differences in how XE presents SQL statements, the “normalized” SQL may not match up. I suggest starting with a new database.
- This only handles rpc_completed and sql_batch_completed events.
- The command-line version isn’t avaiable yet
New in ClearTrace Build 55 (Aug 25, 2019)
- This build doesn’t requires a specific version of SMO. The README.txt describes how to update the .config file to support the version of SMO you have installed. It’s very easy to do.
- This has been tested using the SMO libraries from SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.
- This build only reads extended event files. For trace files, please download the older version below.
- The File Select doesn’t support wildcards. Instead you can browse (open) the directory and select multiple files. This worked much better in my testing. It also doesn’t automatically process all files in order when you select the first one. You’ll need to select all the ones you want to process.
- The database format is the same as ClearTrace for Trace. Due to parsing differences in how XE presents SQL statements, the “normalized” SQL may not match up. I suggest starting with a new database.
- This only handles rpc_completed and sql_batch_completed events.
- The command-line version isn’t avaiable yet
New in ClearTrace Build 55 (Aug 25, 2019)
- This build doesn’t requires a specific version of SMO. The README.txt describes how to update the .config file to support the version of SMO you have installed. It’s very easy to do.
- This has been tested using the SMO libraries from SQL Server 2012, SQL Server 2014, SQL Server 2016, and SQL Server 2017.
- This build only reads extended event files. For trace files, please download the older version below.
- The File Select doesn’t support wildcards. Instead you can browse (open) the directory and select multiple files. This worked much better in my testing. It also doesn’t automatically process all files in order when you select the first one. You’ll need to select all the ones you want to process.
- The database format is the same as ClearTrace for Trace. Due to parsing differences in how XE presents SQL statements, the “normalized” SQL may not match up. I suggest starting with a new database.
- This only handles rpc_completed and sql_batch_completed events.
- The command-line version isn’t avaiable yet
New in ClearTrace Build 54 (Aug 23, 2019)
- This build requires the SQL Server 2017 SMO Library installed on the computer running ClearTraceXE
- This build has been tested against SQL Server 2017 and SQL Server 2016
- This build only reads extended event files
- The File Select doesn’t support wildcards. Instead you can browse (open) the directory and select multiple files. This worked much better in my testing. It also doesn’t automatically process all files in order when you select the first one. You’ll need to select all the ones you want to process.
- The database format is the same as ClearTrace for Trace. Due to parsing differences in how XE presents SQL statements, the “normalized” SQL may not match up. I suggest starting with a new database.
- This only handles rpc_completed and sql_batch_completed events
- The command-line version isn’t avaiable yet
New in ClearTrace Build 51 (Feb 10, 2018)
- 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.