Storage engines: InnoDB and MyISAM

Last reviewed Jun 1, 2026 Content v20260601

Track mode

sql_sandbox

Means

SQL sandbox

Reading

~1 min

Level

intermediate

This lesson

This lesson teaches Storage engines: InnoDB and MyISAM: the SQL patterns, schema habits, and query reasoning you need before advancing in MySQL.

Engine choice is not cosmetic—MyISAM lacks transactions your ORM assumes.

You will apply Storage engines: InnoDB and MyISAM in contexts like: Web apps on shared hosting, ecommerce, and many startups’ first production DB.

Copy MySQL SQL into the mysql client, local MySQL/MariaDB, or DB Fiddle (MySQL dialect)—use DESCRIBE and EXPLAIN where lessons show them. The in-browser lab ships later; mysql client is the practice path now.

When you can explain the previous lesson's ideas without copying example queries verbatim.

InnoDB is default and correct for almost all app tables. MyISAM lacks transactions/FK—legacy only.

Compare

InnoDB	MyISAM
Transactions, FK	No transactions
Row-level locking	Table locks
Crash recovery	Repair tables risk

Show engine

SHOW TABLE STATUS LIKE 'orders';
SHOW ENGINES;

Practice: Run on practice.

Migrate engine

ALTER TABLE legacy_log ENGINE=InnoDB;

Important interview questions and answers

Q: New tables MyISAM?
A: Avoid—InnoDB is default since MySQL 5.5+.
Q: Full-text?
A: InnoDB supports FULLTEXT indexes in modern versions.

Self-check

Default engine for new apps?
One MyISAM drawback?

Tip: ALTER … ENGINE=InnoDB before adding foreign keys to legacy tables.

Interview prep

MyISAM transactions?: No—use InnoDB for app data.
Show engine?: SHOW TABLE STATUS or SHOW CREATE TABLE.

Discussion

Past discussion is visible to everyone. Only logged-in users can post comments and replies.

Starter discussion topics

Convert MyISAM?
FK on InnoDB?

No discussion yet. Be the first to ask a question.