First Responder Kit Release: It’s Too Cold Not To Do A Release

You look just like a snake when you crawl like a worm.

You can download the updated here.

sp_Blitz Improvements

#1310@CferMN reported quite an odd conversion error! Turns out, division was a better idea than multiplication.
#1341: We we missing the newest version of Windows, and we had a broken link. Thanks to @JaySpatzfor letting us know!
#1359: Something we’ve all wanted for a long time: We now tell you which power plan your server is running. It turns out there are three major ones that have been around since like, forever. If you have a weird custom power plan, let us know! Some manufacturers add their own. We are using xp_regread to do this, which we think is less intrusive than xp_cmdshell.

sp_BlitzCache Improvements

There have been quite a few improvements and fixes around the new clickable columns. I do apologize (and take full responsibility for) the bugs. Hopefully this’ll be the end of it, but just saying that… Long story short, did you know that QUOTENAME returns NVARCHAR(258)#1322#1327#1329#1365
#1325: We now grab schema along with store proc/function names
#1349: Improve the handling of some warnings that were firing inconsistently when multiple statements were in a batch
#1331: To improve documentation, I added URLs to a bunch of warnings that were missing
#1366 Add tempdb spills (and a new spill/avg spill sort order), 2017 cu3+ only
#1370: Basic collection of new row goal information, 2017 cu3+ only

Special Note: The tempdb spills being added is a breaking change if you’re logging sp_BlitzCache to a table. This includes if you’re logging to it via sp_BlitzFirst as part of the PowerBi analysis. To fix it without dropping and recreating the table run this:

sp_BlitzFirst Improvements

#1367: Add new CXCONSUMER wait to list of known waits. 2017 cu3+ only (also supposedly coming to 2016 sp2)

sp_BlitzIndex Improvements

#1337@js0505 was kind enough to add a data compression switch to index create statements
#1344: New check for indexes with a bad read to write ratio. These are indexes that do get used by read queries, but get way more writes.

sp_BlitzWho Improvements

Nothing this time around

sp_DatabaseRestore Improvements

Nothing this time around

sp_BlitzBackups Improvements

Nothing this time around

sp_BlitzQueryStore Improvements

All the same stuff as sp_BlitzCache, except the tempdb spill info, because that wasn’t added to query store DMVs.

sp_AllNightLog and sp_AllNightLog_Setup Improvements

Nothing this time around

sp_foreachdb Improvements

Nothing this time around


Nothing this time around


#1350@DaleKBurrell let us know about a fix for illegal XML characters! Thanks!

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.

Thanks for reading!

Previous Post
SQL Server 2017 CU3 adds execution statistics for scalar-valued, user-defined functions
Next Post
SQL Server 2017 CU3 add a new CXCONSUMER wait type

1 Comment. Leave new

  • Henrik Staun Poulsen
    January 12, 2018 4:22 am

    Your comments in the code states that this may not run on SQL Server 2014 and below. I can confirm this (Install-All-Scripts.sql reports an error) , but you might want to put in a warning on the download page as well.


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.