sp_BlitzLock gets better identification of parallel deadlocks, sp_DatabaseRestore uses Ola’s scripts for logging, and lots of bug fixes this month.
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
- Download the updated Consultant Toolkit in your account
- EU customers: check your email for the updated version from Gumroad, our European distributor
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 the /Resources/SQLServerSetup checklist folder over your existing files to replace the SQL scripts.
- Improvement: in @ExpertMode = 1, when we show the top files by read & write stalls, show 20 files instead of 5, and also sort them by the worst stalls. (#2707)
- Fix: ignore FT_IFTSHC_MUTEX waits. (#2697)
- Fix: index suggestions on really long table names could be truncated. (#2680, thanks Ralf Pickel.)
- Fix: columnstore visualization only worked on tables in the dbo schema. (#2683, thanks Ali Hacks.)
- Fix: nonclustered columnstore visualization didn’t report the correct columns. (#2684, thanks Ali Hacks.)
- Fix: if you passed in databases to be ignored, they were still counting against the 50-database limit before we made you pass in BringThePain = 1. (#2693, thanks skrishnan31.)
- Fix: temporal tables had table.schema in the detail names rather than schema.table. (#2694, thanks Mark Hions and Mikey Bronowski.)
- Improvement: better identification of batch mode parallel deadlocks. (#2686, thanks Erik Darling.)
- Fix: no longer reports 0 parallel deadlocks. (#2682, thanks Erik Darling.)
- Fix: corrected time zone conversion issues. (#2674, thanks Merlin Bruno.)
- Fix: filter out incorrect results from the summary. (#2676, thanks Merlin Bruno.)
- Fix: reduce memory grant requirements. (#2691, thanks Ali Hacks.)
- Improvement: commands are now run with CommandExecute so that they get logged if things go wrong. (#2700, thanks Frederik Vanderhaegen.)
- Fix: the new @SkipBackupsAlreadyInMsdb switch was ignoring transaction logs if you were restoring them on the same server where you were taking backups (since they were already in msdb.) (#2710, thanks Greg Dodd, and you can watch a video of him fixing it.)
When you have questions about how the tools work, talk with the community in the #FirstResponderKit Slack channel. If you need a free invite, hit SQLslack.com. Be patient – it’s staffed with volunteers who have day jobs.
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.
Watch Us Working On It
When Greg Dodd found bug #2710 in sp_DatabaseRestore, he live streamed his investigation and the fix:
You can also subscribe to Greg’s YouTube channel if you want to be alerted the next time he streams when he’s working.
And then on the repo maintainer side, I often live stream when I’m merging pull requests. Here’s one of my sessions from this month’s release: