Option to store query store data in a filegroup other than PRIMARY - by brian_carrig

Status : 


Sign in
to vote
ID 2565624 Comments
Status Active Workarounds
Type Suggestion Repros 0
Opened 4/8/2016 6:19:47 AM
Access Restriction Public


Query store data is incredibly useful but depending on activity and settings it can grow to quite a large size. I would like an option to store this data on a filegroup other than PRIMARY. This would allow discretion regarding storage used, reduce the impact to recovery times and give DBAs more flexibility in managing query store data.
Sign in to post a comment.
Posted by Microsoft on 4/2/2017 at 7:56 AM
Thank you for taking time to post this issue! We understand that this could be an important issue for you.

We get a lot of feedback regarding PRIMARY filegroup from the field and many MVPs.  
This item is high on our priory list, but unfortunately, we do not plan to include a fix for this issue in the upcoming release. Although, we might include it as an improvement in future releases.
Posted by Newfangled Old-fashioned Stuff on 2/8/2017 at 2:13 PM
We disallow ALL use of the PRIMARY filegroup on the premise that any use of PRIMARY is unauthorized, and PRIMARY is set to a small size with no autogrow. Since the Query Store on very active servers with non-parameterized workloads grows very, very fast, setting it to a filegroup whose data file is on a specific LUN (based on speed and cost, i.e. a specific storage tier) is vital.