Y'all were busy this summer! The fall release includes new checks for SQL Server 2025's new memory pressure warnings, Azure SQL DB's operations in progress, warnings about not using partitioned statistics where appropriate, plus much more!
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.sp_Blitz Changes
- Enhancement: warn if the server is under memory pressure using SQL Server 2025's new sys.dm_os_memory_history. (#3690)
- Enhancement: reduced false warnings for Linux installations. (#3702, thanks bmercernccer and Tom Willwerth.)
- Enhancement: add @UsualOwnerofJobs parameter so you can warn about logins other than SA if that's your thing. (#3688, thanks James Davis.)
- Fix: servers with German languages could get an error about a subquery returning more than one value. (#3673, thanks Dirk Hondong)
- Fix: skip checks for Managed Instances. (#3685, thanks Klaas.)
sp_BlitzCache Changes
- Fix: implicit conversions would have problems if the parameters involved were really long. (#3681, thanks DForck42.)
sp_BlitzFirst Changes
- Enhancement: warn if the server is under memory pressure using SQL Server 2025's new sys.dm_os_memory_history. (#3692, #3703, thanks Eilandor.)
- Enhancement: warn about ongoing Azure operations like database restores, creations, deletions, setting up geo-replication, changing performance levels or service tiers, etc using sys.dm_operation_status. (#3708)
- Enhancement: when a database is being restored to a new name, show the name. (#3695)
sp_BlitzIndex Changes
- Enhancement: when @SkipStatistics = 0, warn if partitioned tables don't have incremental statistics. (#3699, thanks Reece Goding.)
- Enhancement: add warning for persisted sampling rates. (#3679, thanks Reece Goding.)
- Fix: on a few warnings, instead of filtering out newly created indexes, we were only looking at the new ones, hahaha. (#3705, thanks Bruce Wilson.)
- Fix: possible arithmetic overflow. (#3701, thanks Reece Goding.)
sp_BlitzLock Changes
- Fix: unusual situations might have left folks unable to create permanent output tables. (#3666 and #3667, thanks Filip Rodik.)
sp_BlitzWho Changes
- Enhancement: get live query plans by default on SQL Server 2022 & newer. (#3694)
sp_ineachdb Changes
- Fix: change @is_query_store_on default to null. (#3668, thanks kmorris222.)
Watch Me Working On It
In this live stream, I handle a few pull requests, then add support for SQL Server 2025's new sys.dm_os_memory_health_history:The work continues in this video:
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.