This is a small release just to make sure you don’t forget about us.

We know you’re busy.

You can download the updated FirstResponderKit.zip here.

sp_Blitz Improvements
#1755 – @MisterZeus added a new check for alerts that don’t send information out. I mean, is that even an alert?
#1766 – @jadarnel27 added some code to help folks who have a standard (non-sa) db owner not get warned about their standard user being the db owner.
#1782 – @RichBenner added an additional check to prevent trace file missing/moved errors.

sp_BlitzCache Improvements
#1748 – @RichBenner fixed up a divide by zero issue – what a hero!

sp_BlitzIndex Improvements
#1751 – I’ve attempted to make mode 0 more useful, by including a few more high priority issues. There was just too much missing between Mode 0 and Mode 4 (which gives you everything back that we find).
#1767 – Sometimes checking for duplicates looked like we fired false positives in Mode 0 because we weren’t also filtering the initial results by size
#1778 – @arampendley added code to output additional columns from op stats when you write to a table
#1780 – Fixed an issue where the string we cast a number to wasn’t long enough, and added some formatting to make long strings easier to read.

sp_BlitzFirst Improvements
Nothing this time around

sp_BlitzWho Improvements
Nothing this time around

sp_AllNightLog and sp_AllNightLog_Setup Improvements
Nothing this time around

sp_BlitzQueryStore Improvements
Nothing this time around – WON’T SOMEONE PLEASE USE THE QUERY STORE?

sp_DatabaseRestore Improvements
Nothing this time around

PowerBI
Nothing this time around

sp_BlitzLock
Nothing this time around

sp_BlitzInMemoryOLTP Improvements
Nothing this time around

sp_BlitzBackups Improvements
Nothing this time around

sp_foreachdb Improvements
Nothing this time around

You can download the updated FirstResponderKit.zip here.

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 SQLslack.com. Be patient – it’s staffed with volunteers who have day jobs, heh.

When you find a bug or want something changed, read the contributing.md 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 DBA.StackExchange.com 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.