intermediateDatabase Design — Normalization, Denormalization & Multi-Tenant

When should you denormalize and what are the risks?

When to denormalize: 1) Measured performance bottleneck from JOINs in hot-path queries. 2) Reporting tables that are read-heavy and rarely updated. 3) When the JOIN cost exceeds the storage/sync cost. Methods: add redundant columns (customer_name in orders), materialized views, summary tables, caching layer. Risks: 1) Data inconsistency: redundant data must be kept in sync. Solution: triggers, app

Ready to master this question?

Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.

Next Step

Continue to You're building a SaaS product for 5000 tenants. Each tenant has different data (orders, customers, products). Which database isolation model do you use? →← Back to all SQL questions