Skip to content

Releases: BrentOzarULTD/SQL-Server-First-Responder-Kit

2023-02-15: Bug Fixes for Cache, First, Lock

15 Feb 18:00
@BrentOzar BrentOzar
20230215
9e8f376
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2023-02-15: Bug Fixes for Cache, First, Lock

Thanks to this technique to run SQL Server on Apple Silicon chips, I'm now developing exclusively on my Mac! I've been using a Mac for over 15 years, but in the past, I've always used Windows at some layer somewhere. This time around, it's all Mac the whole way down, which is kinda nifty. Makes my release process easier.

To get the new version:

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_BlitzCache Changes

  • Enhancement: when using @sortorder = 'all', there's a new pattern column to show which metrics sucked about the query, and it's included in the table output. (#3172, thanks Adrian Buckman.)
  • Fix: case sensitivity issues on joining to sys.all_columns. (#3233, thanks sm8680.)

sp_BlitzFirst Changes

  • Fix: QRY_PROFILE_LIST_MUTEX lock timeouts on sys.dm_exec_query_statistics_xml. (#3210, thanks sqlslinger.)

sp_BlitzLock Changes

  • Fix: error converting data type nvarchar to bigint. (#3201, thanks Erik Darling.)
  • Fix: arithmetic overflow in wait_time_hms when wait time added up to more than 2147483647. (#3215, thanks Vlad Drumea.)
  • Fix: string or binary data would be truncated in table tempdb.dbo.#deadlock_owner_waiter. (#3206, thanks johnkurtdk.)

sp_BlitzWho Changes

  • Fix: shows procedure definition even if the current statement isn't in the plan cache. (#3163, thanks Adrian Buckman.)
  • Fix: tempdb allocations did not include internal objects such as worktables and workfiles. (#3174, thanks Adrian Buckman.)

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.

Assets 2
Loading

2022-12-13 Release: Happier Holidays!

13 Dec 18:57
@BrentOzar BrentOzar
20221213main
e10bc83
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2022-12-13 Release: Happier Holidays!

Santa's elves took a break from building toys and shipped a new version of the First Responder Kit. There are some great improvements in here, like a makeover for sp_BlitzLock and much better PSPO compatibility for sp_BlitzCache.

To get the new version:

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_AllNightLog Changes

  • Fix: if a database exists and it's not being log shipped, skip it rather than overwrite it. (#3187, thanks David Wiseman.)

sp_Blitz Changes

sp_BlitzCache Changes

  • Enhancement: show a statement's parent stored procedure where available in SQL Server 2022 to work around the PSPO problem. (#3176, thanks Cody Konior.)
  • Fix: if you asked for the output of @sortorder = 'unused grant' to be written to table, it wasn't working. (#3160, thanks Petr-Starichenko.)

sp_BlitzFirst Changes

  • Fix: Managed Instances were getting errors on Perfmon counters. (#3184, thanks Cody Konior.)
  • Fix: lock timeout errors from sp_msforeachdb. (#3180, thanks Cody Konior.)

sp_BlitzIndex Changes

  • Enhancement: added support for output to table for all modes. (#2774, thanks Tor-Erik Hagen.)
  • Fix: the columnstore index visualization wasn't filtering out tombstone rowgroups. (#3189)
  • Fix: statistics with oddball names would throw errors. (#3162, thanks Jay Holliday.)

sp_BlitzLock Changes

  • Enhancement: in Erik's words, he gave the T-SQL a mommy makeover, including the ability to read from the ring buffer, improve performance, fix data duplicatoin bugs, clean XML to avoid character parsing errors, etc. (#3166, thanks Erik Darling.)

sp_BlitzQueryStore Changes

sp_BlitzWho Changes

  • Enhancement: move session_id and blocking_session_id next to each other for easier blocking troubleshooting. (#3159, thanks David Hooey.)

sp_DatabaseRestore Changes

Bonus changes: Anthony Green kept up the tireless work of keeping the SQL Server versions file up to date.

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.

Assets 2
Loading

2022-10-13 Release: Spooky Scary sp_eletons

13 Oct 14:20
@BrentOzar BrentOzar
20221013
3d782bc
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2022-10-13 Release: Spooky Scary sp_eletons

Spooky scary sp_eletons, send shivers down my spine. There's nothing scary in here, though, just the never-ending march of small improvements to help more people, catch more problems, on more servers.

To get the new version:

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_AllNightLog Changes

sp_Blitz Changes

  • Enhancement: check for most recent log backup using DBCC DBINFO rather than msdb. This way, it works even if the log backups were taken on another AG replica. (#3143, thanks SQL Lambert.)
  • Enhancement: warn about additional dangerous 3rd party modules. (#3149 and #3150, thanks David Wiseman.)
  • Enhancement: works on Amazon RDS even if the server name has been changed. (#3146, thanks Bo Anderson.)

sp_BlitzFirst Changes

  • Fix: returns the Azure SQL DB compatibility that was broken in the last release. (#3139, thanks SJOrderDIRECT.)
  • Fix: even more compatibility for Azure SQL DB. (#3130, thanks DMonlineUK.)

sp_BlitzQueryStore Changes

sp_DatabaseRestore Changes

  • If you use sp_DatabaseRestore and you have servers in different time zones, we'd appreciate your help testing #3113. It's not included in this release because no one has tested it yet. If you can test the StopAt parameter with different time zones and report back in that issue (not here in the comments) about how it worked, that'd be great.
Bonus changes: Anthony Green kept up the tireless work of keeping the SQL Server versions file up to date.

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.

Assets 2
Loading

2022-07-18 Release: SQL Server 2022 Prep

18 Jul 21:54
@BrentOzar BrentOzar
20220719
bc5cca5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2022-07-18 Release: SQL Server 2022 Prep

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:

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

  • 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.)

sp_BlitzCache Changes

  • 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)

sp_BlitzFirst Changes

  • 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)

sp_BlitzIndex Changes

  • 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.)

sp_BlitzLock Changes

  • Enhancement: add spid and wait_resource columns to output. (#3101, thanks David Hooey.)

sp_DatabaseRestore Changes

  • 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.

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.

Assets 2
Loading

2022-04-08 Release: Just a Few Bug Fixes

08 Apr 10:37
@BrentOzar BrentOzar
20220408
28dda84
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2022-04-08 Release: Just a Few Bug Fixes

Wow, talk about stable! The last 3 months have only introduced a series of small bug fixes. I held this release back as long as I could, waiting to see if anything major might get added or if we might get a SQL Server 2022 CTP, but no dice. If there was ever a First Responder Kit release you could skip, it's probably this one. If the specific issues listed here don't affect you, take the morning off.

To get the new version:

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

  • Fix: don't warn people about multiple log files for the same database on the same drive if the sum of the log files is 2TB or more, since that's the max log file size. (#3081, thanks Henrik Staun Poulsen.)
  • Fix: uninstall script works even if databases have different collations. (#3077, thanks Fiander.)
  • Fix: don't crash if sys.plan_guides holds a hint with a double quoted index name. (#3059, thanks Frank Renesnicek.)
  • Fix: arithmetic overflow on large database growth sizes. (#3063, thanks David A. Poole.)

sp_BlitzFirst Changes

  • Fix: the recently updated stats check was only running in the current database. (#3076)

sp_DatabaseRestore Changes

Bonus changes: Anthony Green kept the SQL Server versions file up to date.

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

New Contributors

Full Changelog: 2022010...2022040

Contributors

BrentOzar, Rob-Hague, and 4 other contributors
Assets 2
Loading

Finally, sp_AllNightLog and sp_DatabaseRestore Get Some Love

08 Jan 18:16
@BrentOzar BrentOzar
20220108
658a2d6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Finally, sp_AllNightLog and sp_DatabaseRestore Get Some Love

In this release, sp_Blitz shows some information about clusters and AGs, sp_AllNightLog and sp_DatabaseRestore get some love, and more.

To get the new version:

sp_AllNightLog Changes

  • Enhancement: now works in any database as long as Ola Hallengren's scripts are installed in the same database. (#3009, thanks Nick Fotopoulos.)
  • Enhancement: there's a new configuration record to allow data/log files to be moved to the instance's default directory. (#3046, thanks Dale Hirt.)

sp_Blitz Changes

  • Enhancement: now displays information about clusters and Availability Groups. (#2976, thanks Ragatilao.)
  • Fix: xp_regread no longer errors out if registry keys aren't found. (#2836, thanks ScottL1969 and Andreas Jordan.)

sp_BlitzIndex Changes

sp_DatabaseRestore Changes

  • Enhancement: the @StoPAt parameter is now a real point in time restore, not just stopping at the transaction log before that point, but going up to that moment in time in the last log backup. (#3038, thanks Daniel van der Meulen.)
Bonus changes: Anthony Green kept the SQL Server versions file up to date, and Konstantin Taranov improved the repo's readme.md.

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.

Assets 2
Loading

2021-11-06: Stable, Just Like You

06 Nov 12:13
@BrentOzar BrentOzar
20211106
d7b686a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2021-11-06: Stable, Just Like You

Just like you, the First Responder Kit has been pretty much stable for the last couple of months. There have been a few small changes, but nothing too big. There are a few pending pull requests that folks are working on around an open source setup checklist, better support for Ola Hallengren's scripts, and a new stored procedure to get cluster information. If you want to influence how the production versions of those shape up, head over to the pending pull requests, look at the related issues, and give your feedback.

To get the new version:

sp_Blitz Changes

sp_BlitzCache Changes

  • Fix: when called by sp_BlitzFirst with @OutputType = 'none', don't output a result set. (#2998, thanks Andreas Jordan.)

sp_BlitzIndex Changes

  • Bug: Mode 4 wasn't scripting out the definitions of unique constraints. (#3006, thanks Erik Darling.)

sp_BlitzWho Changes

  • Fix: new @GetLiveQueryPlan parameter, defaults to 0. On some builds of SQL Server 2019, we've seen access violations parsing the XML in live query plans. That's a bug in SQL Server, and we tried to file an issue for it on Connect, and then we tried to file an issue on Feedback.Azure.com, and then we gave up. If you want the live query plan and you aren't worried about SQL Server access violations, turn this switch on. (#3011, thanks Greg Dodds.)

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.

Auto-Generated Changelog

New Contributors

Full Changelog: 2021091...2021110

Contributors

BrentOzar, JamesGally, and 4 other contributors
Assets 2
Loading

2021-09-14 Release - and a Free Class on How to Use It

14 Sep 08:20
@BrentOzar BrentOzar
20210914
47bc8bf
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2021-09-14 Release - and a Free Class on How to Use It

I've slowed the First Responder Kit update frequency down to once every 2 months. I know from firsthand experience working with clients that folks just can't patch quickly enough, hahaha. Folks who want to be on the bleeding edge updates can always use the dev branch in Github, too, getting every new fix the moment it's merged.

Wanna learn how I use it? Register for my free one-day class on Oct 19th or 20th on How I Use the First Responder Kit, or buy the recordings.

To get the new version:

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

  • Fix: if databases aren't online, don't alert on non-default database settings. For example, if someone's got a database offline or in restoring state, they shouldn't be alerted about the delayed durability setting on that database. (#2984, thanks David Schanzer.)
  • Fix: added 1204's explanation when the trace flag is enabled. (#2985, thanks Erik Darling.)

sp_BlitzFirst Changes

sp_BlitzIndex Changes

  • Improvement: scripting for unique constraints. (#2950, thanks Erik Darling.)
  • Improvement: new informational (priority 250) check to tell folks when optimize_for_sequential_key is enabled for an index. Only shows up in Mode 4 since it's a low-priority action that you don't usually have to do anything about. (#2963 and #2991, thanks Erik Darling and FlatlandR.)
  • Improvement: new unindexed foreign key check. (#2964, thanks Erik Darling.)

sp_BlitzWho Changes

sp_DatabaseRestore Changes

  • Improvement: new @SetTrustworthyOn parameter lets you enable this on newly restored databases. (#2981, thanks jesusnac.)
  • Fix: if the database status isn't already in restoring, try to set it into single user mode. (#2960, thanks jesusnac.)

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.

Assets 2
Loading

2021-07-25: The Slowed-Down Dance Mix

25 Jul 08:53
@BrentOzar BrentOzar
20210725
012c213
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2021-07-25: The Slowed-Down Dance Mix

I'm slowing the First Responder Kit update frequency down to once every 2 months. I know from firsthand experience working with clients that folks just can't patch quickly enough, hahaha. Folks who want to be on the bleeding edge updates can always use the dev branch in Github, too, getting every new fix the moment it's merged.

To get the new version:

Consultant Toolkit Changes

  • Improvement: added "Buffer Pool Scan" to the list of things we show from the error log. (Thanks Erik Darling.)
I also 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

  • Improvement: new warning when target recovery interval <> 60. (#2938, thanks Erik Darling.)
  • Fix: sp_Blitz installation was failing on unpatched 2012/2014/2016 builds due to last month's Amazon RDS tweaks. (#2921, thanks Gianluca Hotz.)
  • Fix: output to table wasn't sorting by database, so if you were querying the output table and sorting by ID, you didn't get exactly the same order as the interactive output. (#2937, thanks Johan Parlevliet.)
  • Fix: only alert about the Query Store cleanup bug on SQL Server 2016, not 2019. (#2946, thanks FlatlandR.)
  • Fix: avoid collation errors when pulling the #SkipChecks list from a linked server with a different collation. (#2949, thanks David Schanzer.)

sp_BlitzCache Changes

sp_BlitzFirst Changes

  • Improvement: add total thread time to wait stats views. Total thread time is the total amount of time spent executing queries, whether waiting on something or burning CPU, including parallel child threads. The Github issue is still open because we'll be putting additional work & blogging into this over the coming weeks & months. It's helpful when troubleshooting servers with plan cache amnesia, but I need to write more about how & why. (#2913, thanks Erik Darling.)
  • Fix: enabled the Sleeping Query with Open Transactions alert. (#2922, thanks Eitan Blumin.)
  • Fix: was showing multiple active backups if backup scripts were running from the context of a user database rather than master. (#2941, thanks Adrian Buckman.)

sp_BlitzIndex Changes

  • Fix: corrected "JIndex" to "Index" in one of the warnings. (#2927)
  • Fix: improve uptime measurement on Azure SQL DB. (#2933, thanks David Wiseman.)
  • Fix: the statistics section now shows up even if you're calling sp_BlitzIndex across databases. (#2954, thanks MisterZeus.)

sp_BlitzWho Changes

  • Improvement: new @GetOuterCommand parameter. When set to 1, shows the outer calling query. (#2887, thanks Adrian Buckman.)

sp_DatabaseRestore Changes

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.

Assets 2
Loading

2021-05-30: Fixes and Improvements

30 May 08:31
@BrentOzar BrentOzar
20210530
60352a5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2021-05-30: Fixes and Improvements

If you want to quickly understand the top health and performance issues on your SQL Server, there's no better, easier, free-er way to do it than the open source First Responder Kit.

When you find a bug or want something changed, read the contributing.md file.

To get the new version:

Consultant Toolkit Changes

  • Improvement: on SQL Server 2019, we export a sample query plan for each missing index request. This helps you know the kinds of queries that are triggering missing indexes, and helps you hand-craft an even better index.
That change does mean a new querymanifest.json, but no changes to the spreadsheet. You only need to use the new querymanifest.json if you want that new feature - otherwise, just copy your spreadsheet and querymanifest.json into the new release's folder. (I'm planning a new first tab for the spreadsheet for next month's release, so I don't want you to have to do this work twice if you've been doing customizations - next month's release will be the bigger bang for the buck there.)

sp_Blitz Changes

  • Improvement: if you've accidentally got "show actual execution plans" turned on while running any of the First Responder Kit scripts, it's now automatically turned off inside the proc. (#2911, thanks Daniel Hutmacher and Erik Darling.)
  • Fix: now skips Instant File Initialization check on Amazon RDS because we can't run xp_errorlog. (#2879, thanks Ray Rankins.)
  • Fix: more Amazon RDS compatibility improvements. (#2888, thanks Ray Rankins.)
  • Fix: Agent jobs without failure emails were only showing up in the alerts if they were scheduled. (#2905, thanks Mike Scalise.)

sp_BlitzCache Changes

  • Fix: queries with a duration of more than 2,147,483 seconds (that's 596 hours) would cause an arithmetic overflow. (#2890, thanks Ron MacNeil.)
  • Fix: the Multiple Plans warning was only including the number of plans in the top 10 result set, and now instead shows the total number of cached plans for this query altogether. (#2900, thanks Erik Darling.)
  • Fix: the Many Duplicate Plans warning math is getting closer to accurate. (#2909, thanks Erik Darling.)

sp_BlitzFirst Changes

  • Fix: in the high CPU details in the How to Stop It column, results could be out of order depending on varchar sorting. (#2876 and #2878, thanks Adrian Buckman.)

sp_BlitzIndex Changes

  • Improvement: table-level columnstore visualization on partitioned tables now shows the partition boundaries. (#2860, thanks Nick Papatonis.)
  • Fix: included columns now show their correct sizes in bytes. (#2880, thanks Scott Holiday.)
  • Fix: SQL Server 2019's new sample query plan for missing indexes is now more likely to produce a query that generated the missing index request. I think there's still possibility for edge cases here where this is wrong, and the 2019 user base is so small that we don't have great testing on this yet. (#2883, thanks Greg Dodd and Erik Darling.)

sp_BlitzLock Changes

sp_BlitzWho Changes

sp_DatabaseRestore Changes

  • Fix: the @StoPAt and @OnlyLogsAfter parameters couldn't be used at the same time. (#2898, thanks Greg Dodds.)

SqlServerVersions.sql Changes

  • Fix: the uninstall.sql script now removes this table from any database, not just the current one. (#2893, thanks Andreas Jordan.)
  • Fix: updated the latest build numbers. (#2897, thanks Anthony Green.)

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.

Assets 2
Loading