First Normal Form (1NF)
You'll learn how to structure tables so every column contains only atomic (indivisible) values and eliminate repeating groups.
What Is 1NF?
First Normal Form is the entry-level requirement for normalized database design. A table is in 1NF when:
- Each column contains atomic values — meaning values that cannot be meaningfully divided further
- No repeating groups — there are no columns like "Phone1", "Phone2", "Phone3" storing similar data
- Each cell contains only one value — no lists, arrays, or comma-separated values in a single column
Think of it like organizing a filing cabinet: instead of stuffing multiple documents into one folder slot, you create separate, clearly labeled slots for each distinct piece of information.
Example: Violating 1NF
-- ❌ NOT in 1NF
CREATE TABLE customers (
customer_id INT,
name VARCHAR(100),
phone_numbers VARCHAR(200) -- "555-1234, 555-5678, 555-9999"
);
This violates 1NF because phone_numbers contains multiple values separated by commas — the column is not atomic.
Achieving 1NF
-- ✓ Now in 1NF
CREATE TABLE customers (
customer_id INT,
name VARCHAR(100)
);
CREATE TABLE customer_phones (
customer_id INT,
phone_number VARCHAR(20),
PRIMARY KEY (customer_id, phone_number),
FOREIGN KEY (customer_id) REFERENCES customers(customer_id)
);
Now each phone number has its own row with a single, atomic value. No repeating columns, no comma-separated lists.
Why This Matters
1NF eliminates ambiguity in querying and updating data. You can now easily count phone numbers, search for specific ones, or add new ones without parsing strings.
Key Takeaway: First Normal Form requires atomic values in each column and eliminates repeating groups by creating separate rows for multi-valued attributes.