This quarter's release contains a few advanced warnings & tools, like table output for sp_BlitzLock, new warnings about paused resumable index operations that will be deleted automatically by SQL Server 2022, and a new option to maintain carriage returns and line feeds in sp_BlitzCache's output.
To get the new version:
- Download the updated FirstResponderKit.zip
- Get The Consultant Toolkit to quickly export the First Responder Kit results into an easy-to-share spreadsheet
- PowerShell users: run Install-DbaFirstResponderKit from dbatools
Consultant Toolkit Changes
Updated to this month's First Responder Kit, but no changes to the spreadsheet template.sp_Blitz Changes
- Enhancement: added warning for non-default database scoped configuration changes for SQL Server 2022's options, like PAUSED_RESUMABLE_INDEX_ABORT_DURATION_MINUTES. (#3620, thanks Reece Goding.)
- Fix: @OutputType = 'markdown' would fail if the output had an ampersand in it. (#3610, thanks Roger Dawkins.)
sp_BlitzCache Changes
- Enhancement: new @KeepCRLF parameter lets you retain the carriage returns & line feeds in query text if you want. (#3611, thanks Vlad Drumea.)
sp_BlitzIndex Changes
- Enhancement: added warning for paused resumable index operations. (#3609, thanks Reece Goding.)
- Enhancement: added warning for nonclustered indexes on temporal table history tables, which can break merge statements. (#3618, thanks Reece Goding.)
sp_BlitzLock Changes:
- Enhancement: add table mode output. New parameters for @TargetDatabaseName, @TargetSchemaName, @TargetTableName, etc. (#3614, thanks Erik Darling!)
sp_DatabaseRestore Changes:
- Fix: really long database names would cause the script to fail. (#3605, thanks Philippe Meunier.)
For Support
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.