First Responder Kit Release: Like pssdiag, if pssdiag had parents who cared

I went to the PFE and guess what he told me?
Guess what he told me?
He said girl you better try fix those spinlocks too
No matter what you do, now run this tool

You can download the updated FirstResponderKit.zip here.

sp_Blitz Improvements
#1620@AAvella schooled us on Group Policy registry settings. Someday, we’ll get our act together as a group.
#1631: We’ll now tell you if there’s an update available for your SQL Server version. For most of you, that’s a yes.
#1633: If your plan cache has been cleared yesterday, we check the size of the userstore_tokenpermcache to see if it’s >2gb.
#1634: Update RDS compatibility. We had some recent checks built that didn’t get along well with it.

sp_BlitzCache Improvements
#1612@bertwagner has perfect hair, and perfect syntax. We bow to his knowledge of equals signs.
#1624@digitalohm let us know about a BlitzCache error when looking at large query plans.

sp_BlitzFirst Improvements
#1623@stgioia Doesn’t need to be warned about log shipping running. It should be running. You should check on that.

sp_BlitzIndex Improvements
#1610@way0utwest thinks dta indexes are poorly named, and we agree! Now if you look over in the create t-sql column of sp_BlitzIndex, we’ll give you rename commands for your dta indexes.
#1626: Brent was doing some documentation digging, and decided we should show you the page latch and io waits in dm_db_index_operational_stats when available. That Brent, always wanting to show you things.

sp_BlitzQueryStore Improvements
#1627@OmnipotentOwl is working hard and playing harder in Azure, and fixed up our version checks for Managed Instances. Oh, you don’t have a Managed Instance? Maybe try being less dull. All the cool kids have one.
#1624: Same as BlitzCache

sp_DatabaseRestore Improvements
#1645@digitalohm added the ability to choose between executing and printing commands
#1653@ShawnCrocker Got us on the right path, and switched parts of the code over to use xp_dirtree instead of xp_cmdshell
#1657@ShawnCrocker Fixed up parts of the code that weren’t using CommandExecute.

PowerBI
Nothing this time around

sp_BlitzLock
Nothing this time around

sp_BlitzInMemoryOLTP Improvements
Nothing this time around

sp_BlitzWho Improvements
Nothing this time around

sp_BlitzBackups Improvements
Nothing this time around

sp_AllNightLog and sp_AllNightLog_Setup Improvements
Nothing this time around

sp_foreachdb Improvements
Nothing this time around

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, heh.

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 us!) 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.

You can download the updated FirstResponderKit.zip here.

Previous Post
How The Cloud Turns Performance Tuning Into Cost Savings
Next Post
Does It Matter Which Field Goes First in an Index?

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.

Menu
{"cart_token":"","hash":"","cart_data":""}