Darn May Showers
There's usually something that I think is funny in this space. Instead, I'm going to extend my already extensive day of civic duty by letting you know something interesting about jury duty.
Sometimes, if you show up when they ask you to, they can make you come back for a second day if they don't pick enough people to fill a a jury on the first day.
They'll also be kind enough to give you absolutely no notice and be entirely inflexible about letting you reschedule.
Ah, the joys of not having to worry about customer satisfaction.
Not like us. We care about what each and every one of you thinks about these scripts, for free.
(strums guitar)
sp_Blitz Improvements
#1537: In older versions of SQL Server, if you ran into CMEMTHREAD waits, you'd flip on Trace Flag 8048 at startup and your problems would likely go away. On 2016+, that's the default behavior. But apparently you can still run into CMEMTHREAD. We tried to give you better guidance, but Bob Ward wouldn't let us put his phone number in there. Can't imagine why. Oh well. Hi Bob!
#1552: Ever go to fix a typo and make another typo? Well, that typo is fixed now. Fixed for good.
sp_BlitzCache Improvements
#1522: We sort the second result set more prettier (according to Brent) now. It has good Lo Mein or whatever.
#1525: Busy Loops wording is more consistent. It used to be "frequently executed operators", which was downright confusing at times.
#1528: @RichBenner is a much more forgiving entity than I am. We'll now let you get away with not patching 2017 past CU3 without throwing vicious errors.
#1543: With 2016 SP2 getting released, a bunch of the XML attributes that used to only be in 2017 got back ported. Stuff like tempdb spills and row goal information. You should totally upgrade. I'll be your best friend.
sp_BlitzFirst Improvements
#1545: Eagle Eyed Professional Man With Standard @goochjj noticed that some of the dynamic SQL in sp_BlitzFirst was adding single use plans to the cache. He fixed that with some rather cunning parameterization.
#1388, #1389, #1396: @EmanueleMeazzo did a metric t-rex load of work rewriting the views and view creation syntax so they'll be faster. This has been in the works for a while, but totally worth it. We salute your patience!
sp_BlitzIndex Improvements
#1532: The taller and better looking version of me, @amtwo, spotted some wonkiness with the way we displayed data types for indexes with descending orders. Namely that uh, we weren't showing them. Case expressions are hard sometimes. You just never want them to end.
sp_BlitzWho Improvements
#1527: @TaraKizer noticed that sometimes wait times were wrong for parallel queries. This has been corrected with gusto.
#1531: A lot of times when you're troubleshooting parameter sniffing, you can see the bad plan running. Getting the plan handle to knock it out of the cache is a pain. There's right clicking and XML. Or at least there used to be. Now we surface it in @ExpertMode.
sp_BlitzQueryStore Improvements
#1544: I had made a bunch of changes in BlitzCache to put some checks in @ExpertMode and tidy up URLs, etc. They've all been added here so output should be aligned. There were also some behind the scenes changes to make sure we're only diagnosing parameter sniffing for multi-use plans, and we're not flagging unmatched indexes in trivial plans.
sp_DatabaseRestore 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
PowerBI
Nothing this time around
sp_BlitzLock
Nothing this time around