Two big sets of news this month! The Consultant Toolkit now supports imports to a database so you can track your clients’ health and performance over time, and sp_BlitzCache has a new @AI parameter.

• 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.

@AI = 1 works on any SQL Server, Azure SQL DB, Amazon RDS, etc. @AI = 2 only works on SQL Server 2025 or Azure SQL DB. For more information on how to set it up, check out the documentation.

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

If you’re a consultant that does long term work, maintaining a client’s SQL Servers, then you probably want to track the health and performance of those servers over time. You want data – in a database.

We’ve got a new Loader app that watches a folder for incoming zip files, and when one shows up, it processes the data to load it into a SQL Server (or Azure SQL DB) repository for you.

This means you can set up the Consultant Toolkit at your clients on a scheduled daily task, upload the data to S3 (built in) or use your own file sync methods to get it to the location of your choosing, and then have the data automatically loaded into your database server for you.

To learn more about that, read the PDF documentation included with the Consultant Toolkit.

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.