An execution plan is the database's blueprint for executing your query. It shows the exact steps the optimizer chose: which indexes to use, how to join tables, and in what order to process data. Think of it as a recipe - it tells you not just what the database will cook, but exactly how it will cook it. Reading execution plans is like having X-ray vision into query performance.

Execution plans reveal the truth about query performance. The optimizer generates multiple possible plans, estimates their costs, and chooses the cheapest one. Understanding how to read these plans is essential for optimization.

**Anatomy of an Execution Plan:**

```mermaid

flowchart TD

A[SQL Query] --> B[Parser]

B --> C[Optimizer]

C --> D[Generate Plans]

D --> E[Plan 1]

D --> F[Plan 2]

D --> G[Plan 3]

E --> H[Cost: 1500]

F --> I[Cost: 350]

G --> J[Cost: 5000]

H --> K{Choose Lowest}

I --> K

J --> K

K --> L[Selected Plan]

L --> M[Execution Plan Output]

M --> N[Scan Types]

M --> O[Join Methods]

M --> P[Row Estimates]

M --> Q[Cost Metrics]

style C fill:#e3f2fd

style K fill:#fff3e0

style L fill:#e8f5e9

```

**Key Components of Execution Plans:**

1. **Scan Types** - How data is accessed

2. **Join Methods** - How tables are combined

3. **Row Estimates** - Expected vs actual rows

4. **Cost Metrics** - Relative expense of operations

5. **Execution Order** - Bottom-up or inside-out

**Scan Types Explained:**

```mermaid

flowchart LR

A[Data Access Methods] --> B[Index Seek]

A --> C[Index Scan]

A --> D[Table Scan]

A --> E[Index Only Scan]