Recently, there are have been a few articles about the lack of adoption of Query Store. Note the following:
- Brent Ozar blogged about it in this article Building SQL ConstantCare®: Why People Aren’t Using Query Store.
- Erin Stellato blogged about it in this article Why Aren’t You Using Query Store?
- Bob Ward gives us a nice blog post on how it works SQL Server Automatic Tuning in the Clouds…
To add my official input from the article Bob wrote I will provide this chart that shows the performance improvements we are seeing our systems that we are using Automatic Tuning on:
My company was an early adopter of SQL 2016 and we barely noticed any overhead in turning on Query Store. Our biggest overhead came in the use of tempdb because we process over 20,000 transactions per second on the system causing PATCHLATCH_EX contention in the tempdb. This was resolved in CU5 of 2017 and will not affect your system if you are not processing a high number of transactions per second.
In short, I believe everyone should enable this feature it provides way too much valuable information to not being using in either version of SQL Server 2016 or 2017 to not be using it.
