sp_BlitzQueryStore: The "multiple plans" warning flags up even when you only have one plan.

[ReeceGoding]

sp_BlitzQueryStore: The "multiple plans" warning flags up even when you only have one plan.

[BrentOzar]

@ReeceGoding I have to be honest here: no one's really maintaining sp_BlitzQueryStore. @erikdarlingdata has moved on to start his own company, and he's got an excellent Query Store proc here: https://erikdarling.com/sp_quickiestore/

That's why there isn't really any discussion here. I've been debating whether to deprecate sp_BlitzQueryStore, and I think this is going to be the issue that pushes me over the edge, heh. I'm going to leave it in the FRK for the rest of the year, but announce its deprecation in the next release, and point people over towards Erik's query instead. I'll move sp_BlitzQueryStore over into the Deprecated folder in the first 2025 calendar year release.

[ReeceGoding]

@BrentOzar I must agree with the decision. Like you, I'll be honest here. The truth is that I've had my suspicions about sp_BlitzQueryStore for a while. My to-do list is – soon to be "was" – filled with things to investigate. Every time I looked in to something, I'd find yet more things that screamed that it was little more than a first draft and left me with low hanging fruit to grab.

I've also turned to sp_QuickieStore and think it needs more publicity. Investigating what sp_BlitzQueryStore does that sp_QuickieStore doesn't was on my to-do list. The only feature that I'm sure is missing is the plan analysis parts of sp_BlitzQueryStore. If there's a gap in the Query Store market, it's probably there. It's a shame that we can't just point sp_BlitzCache's plan analysis tools to a Query Store plan somehow.

For peace of mind, here are my top five reasons for supporting your decision.

1. sp_BlitzQueryStore is slow. I've seen it run for half an hour before.
2. It has lots of little things that make it obvious that it sees little maintenance. I did my best to report and patch those out (e.g. typos, double spaces, repeated prints, useless columns, etc), but they should have been spotted years ago.
3. I'm not convinced that there is any documentation on sp_BlitzQueryStore that accurately describes what it does. I've ranted about this before, but the problem became even clearer when I started looking at the code. For example, there is a major step that aggregates many things by day but none of the docs even as much as hint at daily aggregation.
4. What it returns even with sensible choices of parameters is simply overwhelming. This is true even if you set the parameters to lower the number of returned rows.
5. It quite obviously isn't getting used. Search the internet for sp_BlitzQueryStore and you will find shockingly little. Conversely, you can find other items in the First Responder Kit on job openings.