Since its debut in 2016, SQL Server<\/a> Query Store<\/strong> has gained critical features such as wait statistics and automatic plan correction, evolving from a simple logging tool into an adaptive performance tuning partner that minimizes rogue query performance issues across both on-premise and Azure SQL environments.<\/p>\n\n\n\n Organizations still relying on older versions of SQL Server<\/strong> or ignoring the Query Store<\/strong> feature should upgrade and enable it to leverage its comprehensive performance insights and proactive plan management capabilities.<\/p>\n\n\n\n Remember 2016? It was a simpler time when some of us were probably still rocking some on-prem SQL Server hardware, and Query Store had just strutted onto the scene like an eager new intern trying to make a good impression by logging every execution plan in sight.<\/p>\n\n\n\n Well, buckle up. Query Store has spent the last few versions doing some serious leveling up. It’s no longer the new kid on the block. It’s the seasoned performance sleuth you definitely want on your side when queries start going rogue.<\/p>\n\n\n\n Whether you’ve been ignoring it since 2016 (no judgement\u2026 okay, a little judgement<\/em>) or you’re just now poking around the settings, here’s what’s changed and why Query Store is more powerful, flexible, and hopeful than ever before.<\/p>\n\n\n\n Query Store 2017 got a shiny new upgrade, and it brought wait stats to the party. Before this release, Query Store could show you which queries were slow, but it couldn’t tell you why. You basically had to conduct an in-depth forensic analysis using half a toolbox and sheer determination to figure out if a query was bottlenecked by CPU, memory, or just existential dread (okay, maybe not that last one).<\/p>\n\n\n\n But now? Query Store tracks wait stats per query over time, giving you a clearer picture of what’s holding things up. So if your query is taking a nap instead of running like the boss it should be, Query Store can now tell you exactly what it’s waiting for: CPU, memory, or just blocking itself in a tragic twist of fate.<\/p>\n\n\n\n It’s like turning on subtitles for query performance. Suddenly, all that vague slowness starts to make sense.<\/p>\n\n\n\n By the time SQL Server 2019 rolled around, Query Store had clearly been hitting the performance gym, and it brought back some serious gains.<\/p>\n\n\n\n One of its biggest flexes? Automatic Plan Correction.<\/strong><\/p>\n\n\n\n Yes, it’s exactly what it sounds like. Suppose a query suddenly decides to take the scenic route and forget how to be efficient (as they do). In that case, Query Store can automatically roll it back to a previously better-performing execution plan. Like a helpful ghost of queries past. No cape required. Just solid plan history and some behind-the-scenes intervention.<\/p>\n\n\n\n It’s basically the query whisperer: quietly observing, patiently waiting, and then gently nudging your rogue query back into being a decent member of society.<\/p>\n\n\n\n But wait, there’s more!<\/strong><\/p>\n\n\n\n The Query Store UI got a long overdue glow-up in SSMS. Think less \u201cBoring Wall of Metrics\u201d and more \u201cWow, I can actually use this!\u201d Charts you can read. Data that makes sense. Fewer tears. Possibly fewer expletives.<\/p>\n\n\n\n It’s the feature equivalent of SQL Server tapping you on the shoulder and saying, \u201cHey, I noticed this plan is kind of a disaster. Mind if I fix it for you?\u201d<\/p>\n\n\n\n And honestly, when SQL Server volunteers to fix something… you generally say yes. And if the plan still feels like it’s speaking in riddles, just ask us. We’re fluent in Query Store.<\/p>\n\n\n\n Query Store didn’t just get smarter. It went global (Okay, replica global, but still.)<\/p>\n\n\n\n Now thanks to PSP support, SQL Server can generate multiple optimized plans based on actual parameter values. So, instead of your query saying, \u201cThis plan worked once in 2019, and I’m never letting it go<\/em>,\u201d now says, \u201cOh hey, small dataset? Here’s your streamlined plan, little buddy. Giant dataset? I got you covered too.<\/em>\u201d<\/p>\n\n\n\n It’s flexible, smart, and honestly? Long overdue. Goodbye stubbornness, hello adaptability. With these upgrades, Query Store is no longer just a historian. It’s a performance-tuning partner with an eye for nuance.<\/p>\n\n\n\n If you’re using Azure SQL Database or Managed Instance, Query Store is always on<\/em> and always in the mood to analyze. No middle-of-the-night panicked setup. No chaotic switch-flipping. Just pure, eager-to-please performance tracking.<\/p>\n\n\n\n And the best part? Azure gets the newest Query Store features before your on-prem SQL Server even hears about them, like a golden retriever puppy that already knows how to sort XML and also brings you your slippers. Because in the cloud, everything is just a little more.. enthusiastic.<\/p>\n\n\n\n If you’ve been sleeping on Query Store, consider this your friendly wake-up call. It’s not just for troubleshooting anymore. It’s your all-access pass to performance insights, historical query trends, and plan management glory.<\/p>\n\n\n\n Also, if you’re still hanging out with SQL Server 2016 or (gasp<\/em>) something even older? Well, this is your sign to upgrade, my friend. Since Query Store is your workload’s performance coach, you might as well give it both the whistle and the playbook. Otherwise, it’s just yelling ‘DO BETTER’ at your queries from the corner without a game plan.<\/p>\n\n\n\n Not sure where to start? We can help. Whether you’re planning an upgrade, enabling Query Store for the first time, or just need someone to untangle a few stubborn execution plans, we’ve got your back.<\/p>\n\n\n\n Embrace Query Store. Love Query Store. Or at least let it help your queries stop tripping over themselves in production.<\/p>\n\n\n\n\n
Table of contents<\/h2>
From Debutante to Power Player: Key Enhancements Since SQL Server 2016<\/h2>\n\n\n\n
SQL Server 2017: Hello, Wait Stats!<\/h3>\n\n\n\n
SQL Server 2019: Auto-Correct, but for Queries<\/h3>\n\n\n\n
SQL Server 2022: Query Store World Tour<\/h3>\n\n\n\n
\n
At long last, secondary replicas, tired of being left out, were invited to the party. You can now gather Query Store insights even on readable secondaries in Always On Availability Groups. No more performance mysteries in the shadows.<\/li>\n\n\n\n
Finally! Hints you can apply without touching the code. It’s like giving your queries a motivational pep talk, quietly behind the scenes. You got this, little SQL.<\/li>\n\n\n\n
Before SQL Server 2022, queries with different parameter values often clung to a single execution plan like it was their emotional support plan, whether it made sense or not.<\/li>\n<\/ul>\n\n\n\nBonus Perks in Azure SQL<\/h2>\n\n\n\n
So\u2026 Should You Be Using Query Store Now?<\/h3>\n\n\n\n
TL;DR<\/strong><\/h2>\n\n\n\n
\n