Welcome to sp_BlitzCache™ v2.4. This release brings a few changes and bug fixes.
- Fixed a logical error in detecting the output table. Thanks to Michael Bluett for pointing that out.
- Sorting by executions per second finally works. Thanks to Andrew Notarian and Calvin Jones for submitting this week.
- Added a
@query_filterparameter – this allows you to only look at “statements” or “procedures” in the plan cache.
- A check was added to identify trivial execution plans that have been cached. If you’re seeing a lot of these, you need to fix it.
@reanalyzeparameter was added. When set to 0,
sp_BlitzCache™will pull fresh data from the plan cache. When set to 1, though,
sp_BlitzCache™will re-read the results temporary table. This is helpful if you want to save off results in Excel and display results so you can tune queries.
- Added the ability to see a query’s SET options. This is hidden just to the right of the plan in the results grid.
- Moved the
#procstemp table to a global temp table named
##procs. This shouldn’t be a problem because you’d probably get angry if two DBAs were running this stored procedure at the same time any way.
Update: Denis Gobo noticed that sp_BlitzCache™ could potential clobber global temp tables. Global temp table names have been updated in sp_BlitzCache™ to avoid this in the future. Make sure you’re using v2.4.1.