First Responder Kit Release: Sunday, Boring Sunday

This is a modified limited release. After a few new feature releases, we’re achieving stasis.

You can download the updated here.

There are a couple points from the last release that I really need to emphasize:

  1. sp_BlitzCache got some new columns added to the output for tempdb spills. If you want to keep logging it to a table either by itself, or as part of sp_BlitzFirst, you need to either drop the table and let sp_BlitzCache recreate it, or run this command to add the new columns:

ALTER TABLE dbo.YourTable ADD MinSpills BIGINT, MaxSpills BIGINT, TotalSpills BIGINT, AvgSpills MONEY

  1. If you’re running 2017, you NEED TO BE ON CU3 for sp_BlitzCache to run. This is too important of a CU for y’all to be skipping. I’d be doing you a disservice by writing in minor version checks at this early point in the release process.

sp_Blitz Improvements

#1382 @RichBenner went to the mall and balled too hard. When he came back, he brought us a check for stacked instances. Ah, the lovely things you can find with xp_regread
#1393 @elsimer Fixed my fat fingered attempt at fixing XE session names. Apparently Microsoft meant to have one with a space in the name. Ho hum.

sp_BlitzCache Improvements

#1379 Added analysis for tempdb spills. I got so caught up in adding the new sort order, I totally brain farted on adding checks. A smart person would have implemented the easy part first. I am not that smart person.
#1380 Corrected the math used to calculate average spill size. See above comment.

sp_BlitzFirst Improvements

Nothing this time around

sp_BlitzIndex Improvements

Nothing this time around

sp_BlitzWho Improvements

Nothing this time around

sp_DatabaseRestore Improvements

Nothing this time around

sp_BlitzBackups Improvements

Nothing this time around

sp_BlitzQueryStore Improvements

Nothing this time around

sp_AllNightLog and sp_AllNightLog_Setup Improvements

Nothing this time around

sp_foreachdb Improvements

Nothing this time around


Nothing this time around


#1398 Added a proc level recompile hint.
#1395 Added filters to the checks for available proc variables. Not every check can be filtered by every variable, so counts may look a little wonky. We’ll see how it goes. If this is good enough, I’ll leave it. Otherwise, I may move to using a wide table to do all checks from.

For Support

When you have questions about how the tools work, talk with the community in the #FirstResponderKit Slack channel. If you need a free invite, hit Be patient – it’s staffed with volunteers who have day jobs, heh.
When you find a bug or want something changed, read the file.

When you have a question about what the scripts found, first make sure you read the “More Details” URL for any warning you find. We put a lot of work into documentation, and we wouldn’t want someone to yell at you to go read the fine manual. After that, when you’ve still got questions about how something works in SQL Server, post a question at and the community (that includes us!) will help. Include exact errors and any applicable screenshots, your SQL Server version number (including the build #), and the version of the tool you’re working with.

You can download the updated here.

Previous Post
New Speed Controls for Training Videos
Next Post
Froid: How SQL Server 2019 Will Fix the Scalar Functions Problem

2 Comments. Leave new

  • Jonathan Russell
    January 28, 2018 2:39 pm

    Hey Guys, thanks for the update. Something is bugging me though, I never remember where the update is actually downloadable. Even though the link in the update says download it here, it points to which requests your email address. I already have an account so I hit login, and get lost every time, because even when logged in it tells me to signup to receive the update.
    Maybe for logged in customers a link in the tools menu could be added that takes you to a download page that simply downloads the update without requiring filling out forms with information that you already have?

    • Jonathan – you can always click on any of the issue links in the post and download it directly from GitHub.


Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.