Database Design & Normalization Explained (1NF, 2NF, 3NF)

Database Design & Normalization

1 min readPublished 22 Jul 2026

Track your progress. Sign in to mark this guide complete and build your Job Readiness Score.

Good database design organises data so it's consistent and easy to maintain. Normalization is the process of structuring tables to reduce redundancy and avoid anomalies.

Interactive explainer

Database Normalization

Organising tables to remove redundancy — 1NF, 2NF, 3NF.

Tap or hover a part to learn more.

Unnormalized

Redundant & risky.

One big table repeats data (e.g. customer details on every order row). This wastes space and causes anomalies — update the customer in one place and miss others.

Check your understanding

1. What does 1NF require?

2. Why might you deliberately denormalize?

Keep learning

Design & Normalization Keys & Relationships Microsoft DP-900

Practise this in AI Interview™

The normal forms

1NF — atomic values (one value per cell), no repeating groups.
2NF — 1NF plus every non-key column depends on the whole primary key.
3NF — 2NF plus no column depends on another non-key column (no transitive dependencies).
Denormalization — deliberately adding some redundancy back for read performance, a common trade-off in reporting and cloud data systems.

Normalized design prevents update/insert/delete anomalies and pairs with keys & relationships.

Interview Intelligence

How this topic actually shows up in interviews — and how to demonstrate you understand it.

Why employers ask about this

Schema design decisions affect performance and integrity for years, so employers test it.

Technical questions

Explain normalization to 3NF and why it matters.+

Remove redundancy so each fact is stored once; 3NF eliminates transitive dependencies and update anomalies.

Behavioural questions

Describe a trade-off you made in a design.+

Show weighing normalization vs performance and justifying the choice.

Real-world scenarios

“A table repeats customer details on every order.”+

Expected answer: Normalize: split customers into their own table and reference by a foreign key to remove redundancy.

Practise in AI Interview™Rehearse these questions, scored.Plan with Career Coach™A personalised path to your goal.Evidence it in Career Passport™Prove this skill to employers.

Employability Intelligence

Where this knowledge takes you — the jobs, skills and certifications it feeds into.

Relevant roles

Database DesignerData EngineerBackend Developer

Skills you're proving

Schema designNormalizationTrade-offs

Recommended certifications

Microsoft DP-900 (Data Fundamentals)Oracle / SQL certifications

Career progression

Databases & SQL → data engineering/DBA roles.

What employers expect

That you can design a sensible schema and write correct, efficient SQL.

Frequently asked questions

What is normalization?

Structuring tables to reduce redundancy and prevent data anomalies, typically to 3rd Normal Form (3NF).

What is 3NF in simple terms?

Every non-key column depends on the key, the whole key, and nothing but the key.

When would you denormalize?

When read performance matters more than storage efficiency, e.g. reporting or analytics workloads.

Practise what you've learned

Turn this guide into real, evidenced progress

Missiora helps you measure, improve and evidence the capabilities employers actually value — start with the tools best suited to this topic.

Published by

Missiora

Missiora is an AI Employability Intelligence platform. Our resources are researched and reviewed by the Missiora team to help you measure, improve and prove your career readiness.