Skip to content

sp_QuickieStore: split @find_high_impact to isolate OUTER APPLY#704

Merged
erikdarlingdata merged 2 commits intomainfrom
dev
Mar 23, 2026
Merged

sp_QuickieStore: split @find_high_impact to isolate OUTER APPLY#704
erikdarlingdata merged 2 commits intomainfrom
dev

Conversation

@erikdarlingdata
Copy link
Copy Markdown
Owner

Summary

Splits the final @find_high_impact query to isolate the expensive OUTER APPLY for query plans from the scoring/diagnostics logic. Static SQL INSERT for the heavy work, simple dynamic SQL SELECT with APPLY for plans against a small result set.

Tested on SQL2022 and SQL2016.

🤖 Generated with Claude Code

erikdarlingdata and others added 2 commits March 23, 2026 16:11
… 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>
sp_QuickieStore: split @find_high_impact to isolate OUTER APPLY for plans
@erikdarlingdata erikdarlingdata merged commit 5993894 into main Mar 23, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant