Just like you, the First Responder Kit has been pretty much stable for the last couple of months. There have been a few small changes, but nothing too big. There are a few pending pull requests that folks are working on around an open source setup checklist, better support for Ola Hallengren's scripts, and a new stored procedure to get cluster information. If you want to influence how the production versions of those shape up, head over to the pending pull requests, look at the related issues, and give your feedback.
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
sp_Blitz Changes
- Fix: the markdown output didn't include the run date. (#3018 and #3027, thanks Andreas Jordan.)
- Fix: if you had trace flag 1204 on, we were telling you that you had 1222 on. (#3014, thanks James Gallagher.)
sp_BlitzCache Changes
- Fix: when called by sp_BlitzFirst with @OutputType = 'none', don't output a result set. (#2998, thanks Andreas Jordan.)
sp_BlitzIndex Changes
- Bug: Mode 4 wasn't scripting out the definitions of unique constraints. (#3006, thanks Erik Darling.)
sp_BlitzWho Changes
- Fix: new @GetLiveQueryPlan parameter, defaults to 0. On some builds of SQL Server 2019, we've seen access violations parsing the XML in live query plans. That's a bug in SQL Server, and we tried to file an issue for it on Connect, and then we tried to file an issue on Feedback.Azure.com, and then we gave up. If you want the live query plan and you aren't worried about SQL Server access violations, turn this switch on. (#3011, thanks Greg Dodds.)
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.
Auto-Generated Changelog
- Add 17-CU26, 16-SP3 by @Ant-Green in #2999
- Added Cu13 for 2019 by @Ant-Green in #3008
- sp_BlitzCache - Fix output to table if called from sp_BlitzFirst by @andreasjordan in #3000
- Closes #3006 by @erikdarlingdata in #3007
- Fix for issue 2591 - include live query plan only when parameter included by @gdoddsy in #3011
- #2591 sp_BlitzWho GetLiveQueryPlan by @BrentOzar in #3012
- #2591 sp_BlitzWho GetLiveQueryPlan by @BrentOzar in #3013
- #3017 readme.md remove image by @BrentOzar in #3019
- #3018 sp_Blitz rundate in markdown by @BrentOzar in #3020
- Correct 1204 TF list reporting by @JamesGally in #3015
- New Updates by @Ant-Green in #3024
- sp_Blitz - Fix issues with markdown output by @andreasjordan in #3027
- 2021-11-06 release by @BrentOzar in #3028
- 2021-11-06 Release by @BrentOzar in #3029
New Contributors
- @JamesGally made their first contribution in #3015
Full Changelog: 2021091...2021110