It’s fall – time to review your SQL Servers’ configurations, health, backups, and performance before fall turns into fail. To help, we’ve got a new version of the First Responder Kit.
To get the new version:
- Download the updated FirstResponderKit.zip
- Azure Data Studio users with the First Responder Kit extension:
ctrl/command+shift+p, First Responder Kit: Import.
- PowerShell users: run Install-DbaFirstResponderKit from dbatools
- Get The Consultant Toolkit to quickly export the First Responder Kit results into an easy-to-share spreadsheet
Consultant Toolkit Changes
I updated it to this month’s First Responder Kit, but no changes to querymanifest.json or the spreadsheet. If you’ve customized those, no changes are necessary this month: just copy your spreadsheet and querymanifest.json into the new release’s folder.
- Fix: now works when system database collations don’t match. (#3132, thanks Bjorn Nordblom.)
- Enhancement: check for most recent log backup using DBCC DBINFO rather than msdb. This way, it works even if the log backups were taken on another AG replica. (#3143, thanks SQL Lambert.)
- Enhancement: warn about additional dangerous 3rd party modules. (#3149 and #3150, thanks David Wiseman.)
- Enhancement: works on Amazon RDS even if the server name has been changed. (#3146, thanks Bo Anderson.)
- Fix: returns the Azure SQL DB compatibility that was broken in the last release. (#3139, thanks SJOrderDIRECT.)
- Fix: even more compatibility for Azure SQL DB. (#3130, thanks DMonlineUK.)
- Fix: Azure SQL DB Managed Instance compatibility. (#3136, thanks Chris May IVCE.)
- If you use sp_DatabaseRestore and you have servers in different time zones, we’d appreciate your help testing #3113. It’s not included in this release because no one has tested it yet. If you can test the StopAt parameter with different time zones and report back in that issue (not here in the comments) about how it worked, that’d be great.
Bonus changes: Anthony Green kept up the tireless work of keeping the SQL Server versions file up to date.
When you have questions about how the tools work, talk with the community in the #FirstResponderKit Slack channel. Be patient: it’s staffed by volunteers with day jobs. If it’s your first time in the community Slack, get started here.
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 me!) 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.