Updated First Responder Kit with Your January Code Resolutions

I have a sneaking suspicion that a bunch of you made New Year’s Resolutions to contribute to open source, because y’all got started with a bang this year. We’ve even got improvements from Microsoft folks for Azure Managed Instances!

You can download the updated FirstResponderKit.zip here.

sp_Blitz Changes

  • Improvements: skipping checks on Azure SQL DB Managed Instance that aren’t relevant, like system databases on C, Hekaton enabled, and TDE enabled. (#1919, thanks Jovan Popovic.)
  • Fix: if you leave your Amazon EC2 VM name as the default (c’mon, seriously people), we won’t flag it as an RDS server. (#1925, thanks Randy Knight.)
  • Fix: when alerting on backups written to the same drive as databases, ignore tempdb. (#1916, thanks Henrik Staun Poulsen.)

We also added a top-row result warning if checks were skipped because it detected AWS RDS, Express Edition, or Managed Instances – or combinations, like here:

sp_Blitz running on AWS RDS Express Edition

sp_BlitzBackups Changes

  • Improvement: now raises a 16 severity error if it fails due to a nonexistent linked server, making it easier to troubleshoot failures. (#1904, thanks M-Ron.)

sp_BlitzFirst Changes

  • Fix: when sp_BlitzFirst is set up in an Agent job to call sp_BlitzCache, it now checks the SQL Server version before trying to sort by memory grants (which isn’t possible on older versions/patch-levels.) (#1910, thanks M-Ron.)

sp_BlitzIndex Changes

  • Improvement: when you pass in @TableName to do table-level analysis, we added a new result set for statistics histograms at the bottom. (#1900)
  • Improvement: in @Mode = 2 (listing all the existing indexes), we added columns at the far right with the drop and create TSQL. (#1921, thanks Joshua Higginbotham.)
  • Improvement: when @Mode = 4 doesn’t find any results, it now links to FirstResponderKit.org instead of BrentOzar.com. (Trying to remove unnecessary links to us to make it easier for consultants to copy/paste the results as-is for clients.) (#1905)
  • Fix: if you don’t set @BringThePain = 1 and we find >100 partitions, we now raise a level 0 severity error instead of 16. We don’t need to pop you over to the messages tab since there’s a line about the partitions at the top of the result set anyway. (#1914)
  • Fix: @GetAllDatabases = 1 was failing on Amazon RDS when it hit the rdsadmin database because they’re doing something fancy with the resource database. (#1927)

sp_DatabaseRestore Changes

  • Improvement: validate the @Database parameter against the full backup file. (#1894, thanks ShawnCrocker.)

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.

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.

You can download the updated FirstResponderKit.zip here.

Previous Post
How to Think Like the Engine – 2019 Edition
Next Post
Announcing the Official Release of the Consultant Toolkit

4 Comments. Leave new

Leave a Reply

Your email address will not be published.

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