The two most common reasons to denormalize are:
- Performance
- Ignorance
The former should be verified with profiling, while the latter should be corrected with a rolled-up newspaper 😉
I would say a better mantra would be “normalize for correctness, denormalize for speed – and only when necessary”
More Related Contents:
- Is storing a delimited list in a database column really that bad?
- What are database normal forms and can you give examples? [closed]
- Normalization: What does “repeating groups” mean?
- In what way does denormalization improve database performance?
- have address columns in each table or an address table that is referenced by the other tables?
- Minimum no of tables that exists after decomposing relation R into 1NF?
- What’s the better database design: more tables or more columns?
- Normalization in database management system
- Should each and every table have a primary key?
- What is the minimal proof that a database relation is not in BCNF?
- Database development mistakes made by application developers [closed]
- Database, Table and Column Naming Conventions? [closed]
- Surrogate vs. natural/business keys [closed]
- How are super- and subtype relationships in ER diagrams represented as tables?
- What is the best design for a database table that can be owned by two different resources, and therefore needs two different foreign keys? [closed]
- When and why are database joins expensive?
- First name, middle name, last name. Why not Full Name?
- Relational table naming convention [closed]
- What are the design criteria for primary keys?
- When I should use one to one relationship?
- Supertype-subtype database design
- Database optimization orders
- What’s wrong with nullable columns in composite primary keys?
- Best representation of an ordered list in a database?
- NULL permitted in Primary Key – why and in which DBMS?
- What are some best practices and “rules of thumb” for creating database indexes?
- When we need to use 1-to-1 relationship in database design?
- Need help in developing DB logic
- Databse architecture (single db vs client specific db) for Building Enterprise Web (RIA) application on cloud
- Database – Data Versioning [closed]