Things SQL Server vNext Should Address: How Did I Do?

Mom I Did It

A while back, I wrote a bunch of posts about things I’d like to see vNext take care of. In this post, since it’s Friday and I don’t wanna do anything, will round those up and cover whether or they made it in or not.

• Local Variable Estimates: Nope, these still suck.
• Parameter Sniffing: Yes, we got PSP!
• ISNULL SARGability: No, this is still a problem.
• Spools: No, these can still be really rough on query performance.
• Default Isolation Level: This is still only fixed in Azure SQL DB.
• Handling Disjunctive Predicates: Nope, still busted.
• Common Table Expression Materialization: No love here whatsoever.
• Table Variable Modification Performance: Nothing at all.
• Lookup Placement: Zero bueno.
• Optional Parameters: Nada.
• Going From INT To BIGINT: Zilch.
• Making Date Math SARGable: None.
• Adaptive DOP: Yes, we got DOP Feedback!
• Unify Paid Editions: No signs of life here.
• Make Dynamic SQL Easily Traceable: They actually made regular SQL queries in stored procedures untraceable with the PSP feature.
• Add Cost Threshold For Parallelism To Setup Options: Nyet.
• Add Lock Pages In Memory To Setup Options: Nein.

Well, maybe I’ll need to update the list for future releases of SQL Server 2022.

Hmpf.

Thanks for reading!

Going Further

If this is the kind of SQL Server stuff you love learning about, you’ll love my training. Blog readers get 25% off the Everything Bundle — over 100 hours of performance tuning content. Need hands-on help? I offer consulting engagements from targeted investigations to ongoing retainers. Want a quick sanity check before committing to a full engagement? Schedule a call — no commitment required.