Denormalization is the process of attempting to optimize the performance of a database by adding redundant data. It is sometimes necessary because current DBMSs implement the relational model poorly. A true relational DBMS would allow for a fully normalized database at the logical level, while providing physical storage of data that is tuned for high performance. A database management system (DBMS) is a computer program (or more typically, a suite of them) designed to manage a database, a large set of structured data, and run operations on the data requested by numerous users. ... The relational model for management of a database is a data model based on predicate logic and set theory. ...

A normalized design will often store different but related pieces of information in separate logical tables (called relations). If these relations are stored physically as separate disk files, completing a database query that draws information from several relations (a join operation) can be slow. If many relations are joined, it may be prohibitively slow. There are two strategies for dealing with this. The preferred method is to keep the logical design normalized, but allow the DBMS to store additional redundant information on disk to optimize query response. In this case it is the DBMS software's responsibility to ensure that any redundant copies are kept consistent. This method is often implemented in SQL as indexed views. A view represents information in a format convenient for querying, and the index ensures that queries against the view are optimized. See: JOIN, join command in SQL, a relational database keyword. ... SQL is the most popular computer language used to create, modify and retrieve data from relational database management systems. ...

The more usual approach is to denormalize the logical data design. With care this can achieve a similar improvement in query response, but at a cost—it is now the database designer's responsibility to ensure that the denormalized database does not become inconsistent. This is done by creating rules in the database called constraints, that specify how the redundant copies of information must be kept synchronized. It is the increase in logical complexity of the database design and the added complexity of the additional constraints that make this approach hazardous. Moreover, due to constraint evaluation overhead, denormalized database may actually offer worse performance than its functionally equivalent normalized counterpart.

Denormalization should only take place after a satisfactory level of normalization has taken place and that any required constraints and/or rules have been created to deal with the inherent anomalies in the design. For example, all the relations are in Third Normal Form and any relations with join and multi-valued dependencies are handled appropriately.

Examples of a denormalization techniques include:

• storing the count of the "many" objects in a one-to-many relationship as an attribute of the "one" relation
• adding attributes to a relation from another relation with which it will be joined

See also

• Database normalization