This quarter's release includes new checks for SQL Server 2025's new memory pressure warnings, Azure SQL DB's operations in progress, accurate CPU usage on Docker containers, warnings about not using partitioned statistics where appropriate, and 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. 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: warn if Resource Governor is set to cap TempDB usage by percentage, but the TempDB file config won't allow it. (#3721 and #3729, thanks Vlad Drumea.)
- Enhancement: exclude AWS RDS built-in objects from warnings. (#3712, thanks Yoni Sade.)
- Enhancement: add more information about Agent jobs w/o failure emails, like total executions, failed executions, last execution time, and status. (#3732, thanks Vlad Drumea.)
- Enhancement: warn if SQL Server 2025's optimized locking is enabled on a database, but RCSI is not. (#3741)
sp_BlitzBackup Changes
sp_BlitzFirst Changes
- Fix: accurately report CPU usage on Docker containers. (#3710, thanks Reece Goding.)
- Fix: added a missing semicolon to fix a fuzzy underline in VS Code, bless its heart. (#3745, thanks Adrian Burla.)
sp_BlitzIndex Changes
- Enhancement: more flexible handling of database, schema, and table name inputs and outputs. (#3739, thanks Vlad Drumea.)
- Enhancement: sort the temporal tables in Mode 4 output. (#3727, thanks Reece Goding.)
- Enhancement: show JSON indexes in the list of indexes, but none of the data is in place yet, like what column they're on, or sizes, or create/drop statements. Just literally wanna warn people that the object has a JSON index on it. (#3736)
- Fix: some columns could be null when the missing indexes report was run for a specific database. (#3723, thanks Chad Baldwin.)
- Fix: really long combos of database, schema, and table names would throw an error because a dynamic SQL variable wasn't large enough. (#3746, thanks MisterZeus.)
sp_BlitzLock Changes
- Fix: could produce duplicate rows in some cases. This query was hella complex, and I punted it over to ChatGPT, who gave me a fix in less than a second. Fantastic. Is the fix perfect? Probably not. Neither was the original code, ha ha ho ho. (#3711, thanks Tisit.)
sp_BlitzWho Changes
- Enhancement: you can now pass in @OutputTableName = 'schema.table' without using the separate @OutputSchemaName parameter. You can also use brackets around your object names. In Azure SQL DB, where cross-database queries aren't supported anyway, you can now just pass in @OutputTableName without specifying @OutputDatabaseName and @OutputSchemaName. (#3734, thanks Vlad Drumea.)
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.
What's Changed
- sp_Blitz - Fix wording for Trace Flag checks that are dependent on @CheckUserDatabaseObjects by @bwiggin10 in #3716
- #3721 sp_Blitz TempDB RG by @BrentOzar in #3722
- sp_BlitzFirst: Made the sys.dm_os_ring_buffers CPU checks respect Linux always setting system_idle to 0. by @ReeceGoding in #3717
- Fix sp_BlitzBackups.sql problem where Unicode Database Names get mangled in the output. by @OZTPR in #3724
- Bug fix: DB_ID() does not support quoted identifiers by @chadbaldwin in #3723
- #3711 sp_BlitzLock duplicate rows by @BrentOzar in #3725
- Exclude RDS objects and rdsadmin DB from sp_Blitz checks by @yoni-yad2 in #3726
- sp_BlitzIndex: Added an ORDER BY to the temporal table check by @ReeceGoding in #3728
- fix for #3729 - CheckId 271 by @VladDBA in #3731
- changes for #3732 - sp_Blitz CheckID 94 by @VladDBA in #3733
- Changes for #3734 - sp_BlitzWho by @VladDBA in #3735
- #3736 sp_BlitzIndex JSON by @BrentOzar in #3737
- Changes for #3739 - sp_BlitzIndex by @VladDBA in #3740
- #3741 sp_Blitz optimized locking by @BrentOzar in #3743
- fix for #3742 - sp_Blitz returning an extra result set by @VladDBA in #3744
- fix #3746 by changing lots of 4 x spaces into 1 x tabs by @MisterZeus in #3747
- Fix issue #3745 VSCode parsing a THROW in sp_BlitzFirst by @AdrianBurla in #3748
- 2025-11-22 release prep by @BrentOzar in #3750
- Optimized locking check by @BrentOzar in #3752
- 2025-11-22 Release by @BrentOzar in #3751
New Contributors
- @OZTPR made their first contribution in #3724
- @yoni-yad2 made their first contribution in #3726
- @AdrianBurla made their first contribution in #3748
Full Changelog: 2025100...2025112