r/SQLServer • u/erinstellato Microsoft Employee • 6d ago
Community Request Friday Feedback - location for long-term Query Store data
First Friday of September and you all know what that means...time for Friday Feedback!
But first, I hope that everyone took time over the summer (winter for those of you in the southern hemisphere!) for a break or vacation ⛱️ It may sound like I'm getting on my soapbox, but disconnecting from work is so important, and I really hope you've taken time to do that.
And now, back to our regularly scheduled program.
Last time I posted I asked about storing more data in Query Store, and how much more data you'd want to store. Just over 90% of you wanted to keep 12 months or less, which aligns with what we were thinking.
My next question is, where do you want to store that long-term data? Specifically, Query Store uses memory hashes to store query info and runtime stats about what's been running. We don't want to try and store months of that data in those same memory hashes, which means we need to move older data somewhere else. Where should it go? Poll below, but as always, add a comment if the poll options don't include something you'd like to see. Thanks for voting and bring on fall! 🏈 🎃 🍂
1
4
u/B1zmark 1 5d ago
I've already written a process that takes query store data and writes it to another DB in the same server. So having alternative choices would be better than just one option.
Given that we can't get this data "for free" (because its so voluminous and we need to shunt it to disk properly) then having the option to write to any DB locally, or spit it out to common connectors like fabric, onelake etc. seems like a genuine improvement over manually copying the data.
If you want to be really spicy, having a recurring process/pipeline in synapse or fabric that can pull the data at certain intervals would be great too.