CSE Roadmap

Core tier · about 2 hours · 6 parts

Part 1 of 6 · 1 min read

Why this page comes first

In this module you will

  • Read an execution plan's operations, rows, and cost columns.
  • Tell a full table scan apart from an index range scan apart from an index unique scan.
  • Explain why an index lookup can still be slower than scanning the whole table.
  • Use predicate information to see which filter each plan step actually applies.
  • Walk through a real slow-query diagnosis the way a working engineer does.

Earlier pages covered what an index is and how the optimizer picks a plan. This page walks through one real, concrete slow query from start to finish. It is the actual diagnostic habit every later troubleshooting exercise in this level builds on.

Remember this

An index that returns many matching rows and must fetch each one individually can be slower than reading the whole table at once.