2019-09-22: sp_BlitzCache Caches Up with SQL 2019

sp_Blitz Changes

• Improvement: added Uninstall.sql for those of you who wanna nuke it from orbit. (#2080, thanks ShawnPOWER for the request and Emanuele Meazzo for the code.)

sp_BlitzCache Changes

• Improvement: new @sortorder = 'query hash' to detect unparameterized queries that are causing you problems. It's really grouping queries together by query hash, then sorting them by CPU. (#2051, thanks Erik Darling.)
• Improvement: now detects selects that caused writes. (#2063, thanks Erik Darling.)
• Improvement: SQL Server 2019's air_quote_actual plans are back! I figured out a workaround to the bugs I was hitting in 2019: if the datalength of the sys.dm_exec_query_plan_stats plan is longer than the normal plan, then I return it - otherwise I return the normal estimated one. (#2109)
• Fix: updated Paul White's blog URLs to his new site. (#2099, thanks Peter Vandivier.)
• Fix: typo caused @Help = 1 output to have one extra result set. (#2111, thanks TheUserNameSelectionSucks (ha!) for the bug report.)

sp_BlitzFirst Changes

• Fix: @CheckProcedureCache was being skipped for some time zones, especially British Standard Time users. I had to fix this before stepping foot on the Isle of Man again, naturally. (#2096, thanks PlanetMatt for the delightfully easy-to-reproduce bug report.)

sp_BlitzIndex Changes

• Improvement: faster compression analysis on partitioned databases. (#2065, thanks Erik Darling.)

sp_DatabaseRestore Changes

• Fix: last month's release broke on case-sensitive systems, fixed. (#2097, thanks sm8680 for the bug report.)

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.

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.