Okuzeka
Software Engineering vocabulary · Databases and Persistence

Execution plan

Meaning in software engineering, with examples

/ˌɛksɪˈkjuːʃən plæn/nounCore term

In software engineering, execution plan means: The step-by-step strategy the database chooses to run a query, showing which indexes it uses, how tables are joined and how many rows it expects.

In Turkish: yürütme planı, sorgu planı, execution plan

How it is used

Also called a query plan. You get it with EXPLAIN in PostgreSQL and MySQL (EXPLAIN ANALYZE also runs the query and shows real times) or with the estimated and actual plan views in SQL Server. Reading plans is a core skill for tuning slow queries.

Example sentences

  1. The execution plan shows a sequential scan on a ten-million-row table.

  2. Can you share the execution plan from production, not from your laptop?

Common collocations

  • read an execution plan
  • query plan
  • EXPLAIN ANALYZE
  • actual execution plan
  • estimated plan
  • query optimizerThe part of a database engine that looks at a query and the table statistics and picks the cheapest way to run it, producing the execution plan.
  • indexThe position number of an item in an array or list. In most languages counting starts at zero, so the first item has index 0.
  • full table scanReading every row of a table to find the ones a query needs, instead of jumping straight to them through an index.
  • query tuningThe work of making slow queries faster by studying their execution plans and then adding indexes, rewriting SQL or changing database settings.
  • slow queryA query that takes longer than an agreed limit to finish, slowing down the application and using up database resources.

This word in other fields

The same English word can have a different meaning in another field:

More terms: Databases and Persistence

Practise with graded reading

Reading at the right level is the fastest way to make new words stick. Pick free English books by level: