Execution Plans

Before the database can execute an SQL statement, the optimizer has to create an execution plan for it. The database then executes this plan in a step-by-step manner. In this respect, the optimizer is very similar to a compiler because it translates the source code (SQL statement) into an executable program (execution plan).

The execution plan is the first place to look when searching for the cause of slow statements. The following sections explain how to retrieve and read an execution plan to optimize performance in various databases.

Contents

1. Db2 (LUW) : Getting • Operations • Access vs. filter predicates

2. MySQL : Getting • Operations • Access vs. filter predicates

3. Oracle : Getting • Operations • Access vs. filter predicates

4. PostgreSQL : Getting • Operations • Access vs. filter predicates

5. SQL Server : Getting • Operations • Access vs. filter predicates

6. SQLite : Getting • Operations

7. Gupta SQLBase : Getting • Operations