Update README.md - Fixed internal link for sp_BlitzQueryStore #3439
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The hyperlink for the table of contents for
sp_BlitzQueryStore
appears broken. This fixes it.It may also be the case that the "Like BlitzCache, for Query Store" tagline needs changing, but I'm not sure if that or the section heading of "How Has a Query Plan Changed Over Time" should be used. My opinion is that the second of the two should be used. I find that
sp_BlitzQueryStore
will return the same query on multiple rows even if it only has one plan (and throw a "Multiple Plans" warning at the same time), whereassp_BlitzCache
never does. The "How Has a Query Plan Changed Over Time" heading is more faithful to this (because the extra rows are for different time intervals), but the very first line of the docs forsp_BlitzQueryStore
advertises it as similar tosp_BlitzCache
so I'm not sure which jobsp_BlitzQueryStore
is actually intended to do. See issue #3440 .