seniorSQL

What is a full table scan and why is it expensive?

Updated May 17, 2026

Short answer

A full table scan reads every row in a table sequentially.

Deep explanation

Full table scans occur when no suitable index exists or the optimizer decides scanning is cheaper. It is expensive because it increases disk I/O, CPU usage, and memory consumption. It becomes particularly problematic in large-scale datasets.

Unlock with a Pro subscription to view this section.

View pricing

Real-world example

No real-world example available yet.

Unlock with a Pro subscription to view this section.

Upgrade to Pro

Common mistakes

No common mistakes listed yet.

Unlock with a Pro subscription to view this section.

Upgrade to Pro

Follow-up questions

No follow-up questions available yet.

Unlock with a Pro subscription to view this section.

Upgrade to Pro

More SQL interview questions

View all →