Nothing too dramatic this release, just a few bug fixes and improvements:
- Improvement: @Bringthepain = 1 no longer forcibly sets @top to the max. Instead, it's used as a confirmation switch as in the other First Responder Kit procs. For example, if you set @SortOrder = 'all' and @top > 10, and you didn't set @SkipAnalysis = 1, then we require you to set @Bringthepain = 1 to make sure you understand that processing will be slow. (#2172)
- Fix: typo in query syntax caused "incorrect syntax near 'r'" periodically. (#2135, thanks Igal Drayerman for the bug report and Emanuele Meazzo for the fix.)
- Improvement: when you run it for table-level details, like sp_BlitzIndex @TableName = 'Users', the first result set with the list of existing indexes has a new last column with the drop T-SQL. Useful for rapidly building undo/redo scripts. (#2177)
- Fix: when saving the output to table, index definitions longer than 4,000 characters were truncated. Changed output table definition to NVARCHAR(MAX) for the Drop_tsql, Create_tsql, and index_definition columns, and cried just a little. (#2183, thanks Helio Lino de Almeida Filho for the bug report.)
- Improvement: added SQL Server 2019, updated a few versions. (#2181, thanks sm8680 for the bug report and Emanuele Meazzo for the fix.)
sp_DatabaseRestore Changes Awaiting ReviewThere are two pull requests with improvements, but I'll be honest: I'm not really qualified to do code review on these because I don't personally use sp_DatabaseRestore. (I just don't have a use for it myself since most of my work focuses on performance tuning.) If you can give these authors a hand by testing it and making notes in the Github issues, we can get these merged into the main branch:
For SupportWhen 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.