{"id":993,"date":"2019-01-24T10:36:49","date_gmt":"2019-01-24T18:36:49","guid":{"rendered":"http:\/\/3.209.169.194\/blogs\/erin\/?p=993"},"modified":"2019-01-24T13:35:16","modified_gmt":"2019-01-24T21:35:16","slug":"important-query-store-fixes-january-2019","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/erin\/important-query-store-fixes-january-2019\/","title":{"rendered":"Important Query Store Fixes – January 2019"},"content":{"rendered":"

The latest CUs for SQL Server 2016 and 2017 contain some important Query Store fixes that I thought worth mentioning for those of you on either version or those of you looking to upgrade.\u00a0 As of this writing, the current CU for SQL Server 2016 SP2 is CU5<\/a>, and for SQL Server 2017 it is CU13<\/a>.\u00a0 Many times we see fixes that make it into a SQL Server 2017 CU ported back to a SQL Server 2016 build.\u00a0 Interestingly enough, there are some Query Store fixes in 2016 CUs that are not in 2017 CUs.\u00a0 I don’t know if that’s because the issues do not exist in 2017, or if it’s just that they have been fixed yet in 2017.\u00a0 I’m planning to update this post if the fixes are added down the read.\u00a0 So here we go, in descending CU order…<\/p>\n

SQL Server 2017 CU13<\/strong> – FIX: A dump file may be generated when you run the DML internal plan on Query Store enabled database in SQL Server 2017<\/a><\/p>\n

This will occur for anyone using Automatic Plan Correction (which means you will be on Enterprise Edition), as noted by having FORCE_LAST_GOOD_PLAN enabled.\u00a0 You can read more about Automatic Plan Correction here<\/a> (I’m a\u00a0 fan, it’s pretty cool and very helpful for those with small DBA teams and lots of databases, or those DBAs who just have too much on their plate and are constantly putting out fires).<\/p>\n

SQL Server 2017 CU11 and SQL Server 2016 SP2 CU5<\/strong> – FIX: Transactions and log truncation may be blocked when you use Query Store in SQL Server 2016 and 2017<\/a><\/p>\n

I’m aware of multiple companies that have run into this issue and I’m glad to see that the fix was ported back to 2016.\u00a0 I highly recommend getting up to this CU if you can, as the resolution requires a restart (I’ve heard that killing the session_id also works but I haven’t seen that).\u00a0 Also note that the command referenced in the KB article is ALTER DATABASE <databasename> SET QUERY_STORE_CLEAR<\/em>, but I have also seen this when trying to change one of the Query Store options (e.g. changing size or retention days).\u00a0 I am pretty sure it’s any ALTER DATABASE statement that changes Query Store configuration.<\/p>\n

SQL Server 2016 SP2 CU5<\/strong> – FIX: Query Store enabled database takes long time on startup after you apply cumulative update for a SQL Server version<\/a><\/p>\n

Note that this is applicable to systems with Availability Groups, and this is a fix that is not listed for any 2017 CU…I’ll keep watching to see if it shows up.<\/p>\n

SQL Server 2016 SP2 CU4<\/strong> – FIX: Access violation when SQL Server 2016 tries to start Query Store Manager during startup<\/a><\/p>\n

This is also a fix that is not listed for any 2017 CU…<\/p>\n

SQL Server 2017 CU5<\/strong> – FIX: Access violation occurs when Query Store collects runtime statistics in SQL Server 2017<\/a><\/p>\n

I don’t see this fix in any SQL Server 2016 CU, but I’ll keep watching.<\/p>\n

SQL Server 2016 SP2 CU2<\/strong> – FIX: Slow performance of SQL Server 2016 when Query Store is enabled<\/a><\/p>\n

There were many performance-related improvements for Query Store in SQL Server 2017, and huge props to the SQL Server team for getting these back-ported to 2016.\u00a0 At a bare minimum, this is the build you should be running, but I would rather see you on CU5 at this point.<\/p>\n

Note: If you installed CU2 for SQL Server 2017 at any point, please read: Query Store Fix in SQL Server 2017<\/a> for an explanation of what you need to do when you apply a higher CU and why.<\/em><\/p>\n

You may look at this list of fixes and be concerned.\u00a0 Don’t be.\u00a0 These fixes are a good thing!\u00a0 They tell me that more and more people are using Query Store (which is great) and while they have run into issues, I believe it’s because these are bigger systems (see the access violation fix which is for systems with 256 logical cores) or they are interesting\/edge-case workloads, both of which probably don’t exist in Azure, and may be why these issues haven’t been seen previously.\u00a0 I remain, as always, a big proponent of Query Store.\u00a0 If you’re seeing something interesting feel free to comment here or drop me an email.\u00a0 I’ve had some folks do that and I was able to confirm they were seeing a bug and let them know that it would be fixed soon.\u00a0 I’ve had one or two other cases where it’s an issue I haven’t seen and I recommended contacting Product Support.\u00a0 Either way, if you’re unsure about Query Store I have lots of resources to get you started, to get it configured properly, and I answer the question “what about performance?!”.\u00a0 I hope this helps!<\/p>\n