If there was ever a release you could skip, this is probably the one, because you could count this release's changes on just one hand! Well, assuming you were an alien with six fingers. I won't even recap the most important changes - you can just scroll down and read 'em.
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
- 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
Consultant Toolkit Changes
Updated to this month's First Responder Kit, but no changes to the spreadsheet template.sp_Blitz Changes
- Enhancement: when @CheckServerInfo = 1, we now return target & total memory counter outputs for easier troubleshooting of memory pressure. (#3586)
- Fix: when @OutputType = 'markdown', a recently added check could return an invalid XML character, breaking the output. (#3593, thanks Igor Galiney.)
- Fix: if you ran sp_Blitz with VIEW SERVER STATE permissions, and you were the db_owner of master, but you didn't have ALTER TRACE permissions, you would have gotten an error. (#3581, thanks Tisit.)
- Fix: if you had really, really, really big data files, you could get an arithmetic overflow. (#3599, thanks songomajk.)
sp_BlitzIndex Changes
- Enhancement: new first parameter @object Name, so you can now call it even faster by putting an object's name as the only parameter, like 'schema.tablename', for the current database. No need for separate @SchemaName and @TableName parameters, although we kept those to avoid breaking changes. (#3587, thanks Goran Schwarz.)
- Fix: when @debug = 1, we were returning the #BlitzIndexResult set twice instead of once. (#3590, thanks Vincenzo Marchese.)
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
- When your lazy and do not want to fill in all parameters... for: @DatabaseName, @SchemaName, @TableName by @goranschwarz in #3587
- Replace illegal character & in sp_Blitz for Markdown output result by @igaliney in #3594
- sp_BlitzIndex - remove duplicate debug result set by @VincenzoMarchese in #3590
- sp_BlitzIndex change data type from INT to NUMERIC to report on indexes < 1 MB by @stone-de-croze in #3588
- #3586 - adding target & total memory counters to server info section. Closes #3586. by @BrentOzar in #3596
- sp_Blitz - correctly check permissions for sys.traces by @Tisit in #3597
- #3599 sp_Blitz overflow by @BrentOzar in #3600
- 2024-12-28 release by @BrentOzar in #3601
- 2024-12-28 Release by @BrentOzar in #3602
New Contributors
- @goranschwarz made their first contribution in #3587
- @igaliney made their first contribution in #3594
- @VincenzoMarchese made their first contribution in #3590
- @stone-de-croze made their first contribution in #3588
Full Changelog: 2024101...2024122
