Skip to content

sp_QuickieStore: @sort_order tiebreaker for @find_high_impact#706

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

sp_QuickieStore: @sort_order tiebreaker for @find_high_impact#706
erikdarlingdata merged 2 commits intomainfrom
dev

Conversation

@erikdarlingdata
Copy link
Copy Markdown
Owner

Summary

Uses @sort_order as tiebreaker when impact_score ties in @find_high_impact output. Defaults to cpu_share.

🤖 Generated with Claude Code

erikdarlingdata and others added 2 commits March 23, 2026 16:30
…R BY

When multiple queries have the same impact_score, the output order was
arbitrary. Now uses @sort_order to pick a tiebreaker column (cpu_share
by default, or duration/physical reads/writes/memory/executions share).

Tested on SQL2022 with @sort_order = 'physical reads' confirmed in
debug output.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
sp_QuickieStore: add @sort_order tiebreaker to @find_high_impact
@erikdarlingdata erikdarlingdata merged commit 5a8b922 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