Ten years ago, I revealed sp_Blitz at the 2011 PASS Summit, in front of a live audience.
Remember the PASS Summit?
Remember live audiences?
Anyway, to celebrate the 20th anniversary of BrentOzar.com, I've thinking back about the last couple of decades to reminisce about what I've learned, what's changed, and so forth.
Open source kinda sorta existed when I got started with computers as a kid way back in the 1980s. I would buy a programming magazine, prop it up in front of the computer, and actually type programs in by hand on my Commodore 64. Lemme just tell you, that sucked. I've been bad at debugging for four decades.
Today, anybody in the world can install open source utilities in a matter of seconds, make their job easier, increase their value as a professional, and give back to those same open source projects. It's not fair to say that your Github profile is the new resume - most folks just don't have the time to contribute to open source, nor are they allowed to at your day job. However, I think it's fair to say that your Github profile is one of many possible advantages when competing for a job. When someone asks, "Do you have experience with X?" it's amazing to be able to answer, "Yes, and I've even contributed code and documentation to X. Here's my Github profile, and here are some of my interactions with the team."
So with that said, here's this month's new version of the First Responder Kit. It's free - free as in speech - and it thrives thanks to the community members mentioned in the changes below. They're real people just like you with day jobs, and they decided that they wanted to contribute or fix something. They're the heroes that make this whole thing work.
When you find a bug or want something changed, read the contributing.md file.
To get the new version: 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.
ctrl/command+shift+p, First Responder Kit: Import.
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.
sp_Blitz Changes
sp_BlitzAnalysis Changes
sp_BlitzCache Changes
sp_BlitzFirst Changes
As we mention in the documentation, Azure SQL DB isn't technically supported by any of the First Responder Kit scripts because Azure SQL DB doesn't have all of the cool diagnostics stuff that we get on-premises, like sp_MSforeachdb. However, at some point in the future, we'll officially support a lot of them up there, and this month's changes inch us towards that.
sp_BlitzIndex Changes
sp_BlitzLock Changes
sp_BlitzWho Changes
sp_DatabaseRestore Changes
For Support
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.