The big news in this release is the new @ai parameter for sp_BlitzCache.
- Set @ai = 1, and get a prompt you can copy/paste into the AI of your choice to help you tune the query.
- Set @ai = 2, and we'll actually call ChatGPT or Google Gemini for you and return the advice.
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 quarter's First Responder Kit, but no changes to the spreadsheet template. This release adds behind-the-scenes code to export to JSON, and then import that data into a database so you can keep a centralized database with all of your clients' diagnostic data on their servers for easier analysis. If you're interested in testing that, email me at help@brentozar.com with a short description of your use case.sp_Blitz Changes
- Enhancement: the check for an AG secondary getting behind now works even if the secondary is offline. (#3783, thanks iant-at-scc.)
- Enhancement: the check for linked servers now shows the name if the data source isn't configured. (#3785, thanks Steve Earle.)
- Fix: remove unused line from sp_Blitz documentation. (#3760, thanks Reece Goding.)
sp_BlitzCache Changes
- Enhancement: add new @ai parameter to get advice from AI. (#3669, thanks Kori Francis for the debugging.)
sp_BlitzFirst Changes
- Fix: improve performance when thousands of sessions have open transactions. (#3766, thanks Giorgio Cazzaniga.)
sp_BlitzIndex Changes
- Enhancement: new check for heaps with page compression enabled. (#3780, thanks Vlad Drumea.)
- Fix: case sensitivity error with new is_json column. (#3757, thanks michaelsdba.)
- Fix: when debug = 1, not all result sets were shown. (#3776, thanks Vlad Drumea.)
- Fix: typo with wrong priority for missing index warning. (#3778, thanks Vlad Drumea.)
sp_BlitzLock Changes
- Enhancement: bail out early if no rows were found in the target table. (#3787, thanks Erik Darling.)
- Fix: table existence checks now handle situations where some, but not all, tables were set up. (#3789, thanks Erik Darling.)
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.