Query Store Indexes

Arthur Daniels shows what you can learn from the indexes on Query Store tables:

It looks like internally Query Store is referred to as plan_persist. That makes sense, thinking about how the Query Store persists query plans to your database’s storage. Let’s take a look at those catalog views vs their clustered and nonclustered indexes. I’ve modified the query a bit at this point, to group together the key columns.

This lets you see how the Query Store authors expected us to use these tables.  Which isn’t always how people use them…

Related Posts

Query Store UserVoice Requests

Erin Stellato has a compendium of Query Store UserVoice requests: In early January Microsoft announced that Connect, the method for filing SQL Server bugs and feature requests, was being retired.  It was replaced by User Voice, and any bugs/requests were ported over.  Sadly, the votes from Connect did not come across to User Voice, so I went […]

Read More

Query Store And Multiple Plans Per Query

Kendra Little follows Betteridge’s Law: Can I Force Multiple Plans for a Query in Query Store? Nope. At least, not right now. I started thinking about this when I noticed that the sys.sp_query_store_unforce_plan requires you to specify both a @query_id and a @plan_id. If there’s only ever one plan that can be forced for a […]

Read More

Leave a Reply

Your email address will not be published. Required fields are marked *


March 2018
« Feb