File this under…
Things probably only I care about. But the Showplan Schema for SQL Server 2017 popped up… well, I caught it last night. I probably could have written this sooner, huh?
So what’s new? Well, if I compare the 2016 SP1 schema using KDiff, a few things stand out. Some I’ve blogged about, and some… I have no idea what they are.
The first thing that shows up is the statistics used by the query. Both sp_BlitzCache and sp_BlitzQueryStore support this.
After that is support for Interleaved Execution and Adaptive Joins. Unfortunately, from what I’ve been able to see, the Interleaved stuff is in actual plans only. Adaptive Joins are flagged in both cache-spelunking procs, but there’s not much analysis yet. Still gotta see if there are patterns to look for.
There are a few odds and ends line that build plumbing in for AJ/IE, and then there’s this! Jackpot!
So here’s the weird one.
I have no idea what these are for. If anyone from Microsoft wants to drop me a line, I promise I’ll… tell or not tell people about it. Whatever works for you.
After that, there’s this curious bit.
The reason this is curious is because TOP WITH TIES
syntax has been around forever. I wonder what this is around for.
Nothing else was all that different or interesting. Which I guess means I can leave the plan cache procs alone.
Just kidding!
Thanks for reading!
2 Comments. Leave new
Just a guess but it could be that Top N Sort operator now supports queries using
with ties
. If you addwith ties
to a query that have the Top N Sort you will instead get one Sort and one Top operator (SQL Server 2016).Ooh that’s a great point! I didn’t think of that.
Obviously.