Summer has turned the corner. Sure, right now the First Responder Kit is wearing its swimsuit, basking in the sun, but already as we speak, the days are getting shorter. It’s only going to be a matter of time before the Pumpkin Spice release of the First Responder Kit. Go outside and take a walk, work on your tan while you still can.
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
Consultant Toolkit Changes
I updated it to this month’s First Responder Kit, but no changes to querymanifest.json or the spreadsheet. If you’ve customized those, no changes are necessary this month: just copy your spreadsheet and querymanifest.json into the new release’s folder.
- Enhancement: ignore SQL Server 2022’s default In-Memory OLTP usage for TempDB if it’s low. (#3110)
- Enhancement: ignore SQL Server 2022’s idle POPULATE_LOCK_ORDINALS wait. (#3105)
- Enhancement: ignore queries in system databases that have recompile hints. (#3119, thanks Erik Darling.)
- Fix: typo on a check. (#3116, thanks Andreas Jordan.)
- Fix: should no longer get arithmetic overflow errors on servers with huge numbers of reads and writes that overflowed bigints. (#2980, thanks sunsickteck and RihoA.)
- Fix: the Average Max Memory Grant column contents formula was wrong. (#3120, thanks MrTCS.)
- Fix: make warning capitalization more consistent. (#3096)
- Enhancement: the file stats output section now shows the database name at the far right. (#3118)
- Fix: only repopulate the ##WaitCategories table if its contents are older, not newer. (#3092)
- Fix: lower memory usage on SQL Server 2019 instances that are facing a bug in an out-of-control number of entries in sys.dm_db_missing_index_group_stats_query. This DMV is only supposed to have 600 rows, but it looks like in some older 2019 CUs, the number of recommended index plans wasn’t capped the way BOL says it should be. (#3085, thanks Paul Neering.)
- Enhancement: add spid and wait_resource columns to output. (#3101, thanks David Hooey.)
- Enhancement: look for Ola’s CommandExecute proc in the current database, so it should be supported in more non-system-database scenarios. (#3094 and #3095, thanks Ben Wiggins.)
- Fix: case sensitivity typo involving BackUpFile. (#3100, thanks Maarten Clardij.)
Bonus changes: Anthony Green kept the SQL Server versions file up to date.
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.
Hi Brent, I’m a fairly new DBA (about 2 years now). I just started using sp_blitz and we got a finding that “TDE Certificate Not Backed Up Recently”. However, we do backup the certificates upon our initial set ups of any new servers. Is this implying that the certificate should be backed up on a regular basis? We are able to use the certificates whenever we’re doing restores to a lower environment so I’m just wondering what the impact is and why this is considered a finding that sp_blitz reports.
Yes, the certs should be backed up on a regular basis. Make sure to click the “more info” link to understand why. Cheers!