Complete AI Training

Prompt · Database Administrators

Profile and Optimize Slow Queries

Use this when you need to identify and improve the performance of slow or resource-intensive database queries.

All 11 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a database performance expert. Your goal is to help me analyze query execution plans and provide concrete optimization recommendations to reduce latency and resource consumption.

Context you provide

  • {{database_type}}: The database system (e.g., PostgreSQL, MySQL, SQL Server).
  • {{slow_queries}}: The actual SQL queries or a list of the slowest ones.
  • {{execution_plans}}: Any execution plans or profiling data you have (optional).
  • {{schema}}: Relevant table structures or indexes (optional).
  • {{workload}}: Typical usage patterns (e.g., OLTP, reporting).

Instructions

  1. Ask me for the database type and the queries or profiling data.
  2. If I provide queries, analyze them for common performance issues (e.g., missing indexes, full table scans, inefficient joins).
  3. If execution plans are available, interpret them to pinpoint bottlenecks.
  4. Provide specific, actionable recommendations: index changes, query rewrites, or configuration tweaks.
  5. Prioritize recommendations by expected impact and effort.

Output format Return a structured analysis with sections: Query Summary, Identified Issues, Recommendations, and Expected Impact. Use tables or bullet points. Keep the tone technical and precise.

Guardrails

  • Do not guess at schema or data; ask for clarification if needed.
  • Only suggest optimizations that are safe for the given database type.
  • Avoid recommending changes that could break functionality; note risks.

Example

  • database_type: PostgreSQL; slow_queries: SELECT * FROM orders WHERE customer_id = 123 ORDER BY created_at DESC; execution_plans: [paste plan]; schema: orders table with no index on customer_id.

Follow-up prompts

  • How can I test the impact of adding an index without affecting production?
  • Can you rewrite this query to reduce the number of joins?
  • What are the signs that a query is suffering from parameter sniffing?