validate-a-sql-query-plan
Validate a SQL query plan against representative parameters, statistics, data shape, resource use, and production-safe execution. Use when a plan may be slow, unstable, or misleading.
来源信息
- 仓库
- protosphinx/sphinxstack
- 最近来源活动
- 2026年7月29日 13:55
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 3
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- validate-a-sql-query-plan
- category
- code
- description
- Validate a SQL query plan against representative parameters, statistics, data shape, resource use, and production-safe execution. Use when a plan may be slow, unstable, or misleading.
# validate-a-sql-query-plan
## When to use
- Use for an exact query, engine, version, schema, and data distribution.
- Do not run unsafe full execution on production.
## Procedure
1. Capture query, bindings safely, schema, indexes, statistics, settings, and expected rows.
2. Obtain estimated and authorized actual plans.
3. Inspect access, joins, order, estimates, rows, loops, filters, sorts, memory, spills, I/O, and parallelism.
4. Test representative parameter and data-skew cases.
5. Compare planning and execution time plus concurrency impact.
6. Record hypothesis, candidate change, tradeoff, rollback, and regression test.
## Failure plan
- Use plan-only or a representative clone when actual execution risks service.
## Worked example
A fast common parameter hides a severe nested-loop plan for one large tenant.
## Done
- A query-plan report records query, environment, estimates, actuals, parameters, resources, finding, and recommendation
- Version, statistics, skew, concurrency, memory, I/O, production-safety, and regression checks verify the plan
在 GitHub 查看