Onstage at SQL Intersections in Orlando this morning, Bob Ward announced that Query Store will be available in all editions of SQL Server 2016.
This is awesome, because Query Store is a fantastic flight data recorder for your query execution plans. It’ll help you troubleshoot parameter sniffing issues, connection settings issues, plan regressions, bad stats, and much more.
I’m such a believer in Query Store that sp_Blitz® even warns you if Query Store is available, but isn’t turned on.
Wanna learn what it is and how to use it? Books Online’s section on Query Store is a good place to start learning, and check out Bob’s slide deck and resource scripts.
And oh yeah – Argenis Fernandez and I had a little bet. He bet that Query Store would be fully functional in Standard Edition, and I bet that it wouldn’t. I’ve never been happier to lose a bet, and I made a $500 donation to Doctors Without Borders this morning. Woohoo!
Update 4/21 – note the comment below from Bob Ward, who clarifies that this wasn’t quite ready for release yet, and feature decisions may not have been made yet.
7 Comments. Leave new
I wonder if there are some performance impact while Query Store is enabled and how (if supported) it works together with high availability groups.
Brent,
Great turnout at SQLIntersection and I love the enthusiasm that exists for Query Store for SQL Server 2016 and Azure SQL Database. It was not my intention to make an official announcement of the availability of Query Store in upcoming editions of SQL Server 2016. We are still working on the details of feature availability in the various editions of SQL Server 2016 including Query Store. Your donation sounds like to a great organization so if it does not show up in Standard Edition I’ll cover your donation of $500. And if to does make that edition, I’ll be happy to match your donation.
Thank You,
Bob Ward
Microsoft
Bob – dang! I was really excited there. Ah, well, I’m gonna hold out hope! Thanks for the kind offer of matching the donation, too.
I hope to see this in Standard! We have a lot of legacy SQL Servers that we will be migrating to newer versions soon. This would definitely be a reason to hold off until the SQL 2016 release instead of going with 2014.
Limiting number of features in Standard Edition is like shooting yourself in the foot. The ISVs need to find lowest common denominator so they don’t use Enterprise features most of the time.
It would be more reasonable to have (almost) all features equally in Standard and Enterprise and limit just the processing power (i.e. the amount of RAM and CPUs/cores supported). This way it would be way easier to create modern applications using new features of SQL Server. I’m really hoping to see that in the next version of SQL Server.
And also I wonder why they didn’t implement code to handle scans using GPGPU. That would bring massive speed enhancements to the table.
Endrju – interesting. Have you filed a request for GPU-assisted queries at http://connect.microsoft.com?
Endrju – I second that. As the project scales, the budget increases. MS would be better served if all features could scale from standard to enterprise. Resigning a system when you migrate from Standard to Enterprise so it can now use those enterprise features does not give us a warm and friendly feeling towards MS. Enterprise should just relate to scale: CPU’s, memory, size.
Also, I’m reading differing opinions on whether Query store should run always, or just for short periods. It will be great to get some solid testing data on what would be the best approach.