Database Query Explainer

The Challenge

Complex SQL queries are hard to understand and debug. Junior engineers struggle to read inherited queries, and even experienced developers spend time deciphering optimization opportunities.

The AI Desk Solution

AI Desk explains queries in plain language, identifies performance issues, and suggests optimizations.

The Workflow

Step 1: Query Submission

Input: Complex SQL query
Sources: Query execution plan, table stats

Step 2: Analysis

• Logic explanation
• Performance review
• Optimization opportunities

Step 3: Explained & Optimized

📊 Query Analysis

ORIGINAL QUERY
SELECT u.*, COUNT(o.id) as order_count
FROM users u
LEFT JOIN orders o ON u.id = o.user_id
WHERE u.created_at > '2025-01-01'
GROUP BY u.id
HAVING COUNT(o.id) > 5
ORDER BY order_count DESC
LIMIT 100;

PLAIN ENGLISH EXPLANATION
This query finds the top 100 users who:
├── Signed up after January 1, 2025
├── Have placed more than 5 orders
└── Sorted by most orders first

It returns all user details plus their
order count.

EXECUTION ANALYSIS
├── Estimated rows scanned: 2.4M
├── Execution time: 3.2 seconds
├── Full table scan: Yes (users)
├── Index used: orders.user_id
└── Sort in memory: No (disk spill)

ISSUES IDENTIFIED

🔴 Missing Index
├── users.created_at needs index
├── Current: Full table scan
└── Impact: 10x slower than needed

🟡 SELECT * Usage
├── Fetching 24 columns
├── Only need ~5 for display
└── Impact: Memory + network

🟡 Expensive GROUP BY
├── Grouping on primary key
├── Consider subquery approach
└── Impact: Memory pressure

OPTIMIZED VERSION
[Rewritten query with improvements]

EXPECTED IMPROVEMENT
├── Execution: 3.2s → 0.3s
├── Rows scanned: 2.4M → 180K
└── Memory usage: -60%

Value Proposition

• Time Saved: 30 minutes per query
• Learning Tool: Builds SQL skills
• Performance Gains: Optimized queries