sp_QuickieStore: split @find_high_impact to isolate OUTER APPLY for plans#703
Merged
erikdarlingdata merged 3 commits intodevfrom Mar 23, 2026
Merged
sp_QuickieStore: split @find_high_impact to isolate OUTER APPLY for plans#703erikdarlingdata merged 3 commits intodevfrom
erikdarlingdata merged 3 commits intodevfrom
Conversation
sp_QuickieStore: rewrite representative text query for @find_high_impact
… APPLY The final output query combined scoring, diagnostics, and an OUTER APPLY to Query Store for plans in one statement with a LOOP JOIN hint. The APPLY dragged performance on large Query Stores. Split into two steps: - Step 6: Static SQL INSERT into #hi_output with all scoring, diagnostics, and text — no dynamic SQL, no plan fetch, no LOOP JOIN hint - Step 7: Simple dynamic SQL SELECT from #hi_output with OUTER APPLY for plans against a small, pre-filtered result set Tested on SQL2022 and SQL2016. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
The final output query combined scoring, diagnostics, and an OUTER APPLY to Query Store in one statement with a LOOP JOIN hint. The APPLY dragged on large Query Stores.
Split into:
#hi_output— all scoring, diagnostics, text. No dynamic SQL, no plan fetch, no LOOP JOIN#hi_outputwith OUTER APPLY for plans against a small pre-filtered result setTest plan
🤖 Generated with Claude Code