query-optimization-agent

To optimize slow SQL queries, analyze the EXPLAIN execution plan to identify full table scans and bad join orders. Apply index recommendations and rewrite JOINs or subqueries to reduce latency and resource usage.

Fixing N+1 query patterns involves rewriting application code to batch related database queries or use JOINs. This eliminates repeated single-row lookups, significantly reducing database access latency and improving page load speeds.

Analyzing an EXPLAIN plan reveals performance bottlenecks by highlighting costly operations like full table scans and inefficient join orders. Interpreting this output guides targeted SQL rewrites and index creation.

Yes, providing table schemas, current indexes, and slow query logs is required for SQL query tuning. This context enables accurate index recommendations, execution plan comparisons, and performance improvement estimates.

Database indexes improve read performance for query optimization but introduce trade-offs for write overhead and maintenance. Evaluate these trade-offs to balance faster SELECT operations against slower INSERT, UPDATE, and DELETE execution.

A SQL query performs a full table scan instead of using indexes due to missing or inappropriate indexes, or bad join orders. Analyzing the EXPLAIN plan identifies these costly operations to recommend appropriate index DDL.