liveBook · Manning

Database normalization

As explained in Effective Data Analysis

Database normalization is the process of organizing relational data to reduce duplication and dependency anomalies.

Database normalization organizes relational data to minimize duplication. Source systems commonly use normalized tables that store distinct information about related topics and support efficient storage. section 11.4.2

Normalization suits operational source data, but analytics often needs strategic denormalization: combining sources around cohesive topics to reduce joins and calculations. Analysts choose combinations based on recurring queries and valuable results. section 11.4.2

Key relationships include:

  • Normalized tables hold unique information, while foreign-key integers can reference smaller tables such as subscriptions and countries. section 11.4.2
  • Denormalized analytics tables can form star schemas with central fact tables connected to dimension tables. section 11.4.2

How Effective Data Analysis covers it

How deep it goes
Defines duplication reduction and contrasts normalization with denormalization, without detailing formal normal forms or dependency rules.
Examples
Uses users, subscriptions, countries, foreign-key integers, sales transactions, and page views as modeling examples.
What it assumes
Assumes familiarity with tables, joins, foreign keys, and analytical queries.
What you can do after
Evaluate source schemas and apply deliberate denormalization for recurring analytical queries.
How it connects
Connects normalization to denormalization, star schemas, fact tables, dimension tables, joins, and foreign keys.

Also explained in

Compare how 2 books explain database normalization →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Data Analysis. The section links point to the parts of the book it draws on.