Database Query Performance Optimizer
Diagnoses a slow SQL query from its plan and proposes indexes, rewrites, and schema changes with measurable impact.
Prompt
ROLE: You are a database performance engineer who optimizes SQL without sacrificing correctness. CONTEXT: - Database engine & version: [e.g., PostgreSQL 16] - Slow query: ```sql [PASTE_QUERY] ``` - EXPLAIN / EXPLAIN ANALYZE output: [PASTE_PLAN_OR 'not available'] - Table sizes & relevant indexes: [ROW_COUNTS, EXISTING_INDEXES] - Access pattern: [HOW_OFTEN, READ_HEAVY_OR_WRITE_HEAVY] TASK (think step by step): 1. Interpret the query plan: identify the dominant cost (seq scans, nested loops, sorts, spills). 2. Explain WHY it is slow in terms of rows examined vs. returned. 3. Propose fixes ranked by expected impact: index additions, query rewrite, schema/denormalization, or config. 4. For each index, give the exact DDL and explain selectivity and column order. 5. Note write-path and storage trade-offs of every index you add. OUTPUT FORMAT: ## Diagnosis ## Recommendations (ranked; each: change | rationale | expected effect | trade-off) ## Exact DDL / Rewritten Query ## Verification Plan (what to re-measure) CONSTRAINTS: - Preserve exact result-set semantics unless you flag a change explicitly. - Do not recommend indexes that duplicate existing coverage. - Quantify expectations relatively (e.g., 'eliminates the sort'), never with fabricated absolute timings.
How to use this prompt
- 1
Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.
- 2
Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.
- 3
Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueAsks the model to reason step by step before answering — ideal for multi-step, logical, or analytical tasks.
Learn this techniquePins the response to a defined structure so it drops straight into your workflow.
Learn this techniqueRecommended models
Build on this prompt
Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.
More in Software Engineering
Production Incident Root Cause Analysis
Drives a disciplined RCA from symptoms to root cause and prevention, separating contributing factors from the true trigger.
Security-Focused Code Review For Pull Requests
Reviews a diff specifically for security vulnerabilities, mapping findings to severity, exploit path, and concrete fixes.
Legacy Code Refactoring Strategist
Plans a safe, incremental refactor of tangled legacy code with characterization tests and reversible seams.
API Contract Designer With OpenAPI Output
Designs a consistent, versioned REST resource and emits a ready-to-use OpenAPI 3.1 fragment plus error model.