Editing Denormalization

{{Refimprove|date=May 2008}}
{{short description|Strategy used on previously-normalized databases}}
'''Denormalization''' is a strategy used on a previously-[[Database normalization|normalized]] database to increase performance. In [[computing]], denormalization is the process of trying to improve the read performance of a [[database]], at the expense of losing some write performance, by adding [[Redundancy (information theory)|redundant]] copies of data or by grouping data.<ref>G. L. Sanders and S. K. Shin. [https://web.archive.org/web/20171201030308/https://pdfs.semanticscholar.org/2c79/069c01ba8d598f32e61fe367ef6d261a0cb4.pdf Denormalization effects on performance of RDBMS]. In Proceedings of the HICSS Conference, January 2001.</ref><ref>S. K. Shin and G. L. Sanders. [http://portal.acm.org/citation.cfm?id=1217757 Denormalization strategies for data retrieval from data warehouses]. Decision Support Systems, 42(1):267-282, October 2006.</ref> It is often motivated by [[Computer performance|performance]] or [[scalability]] in [[relational model|relational]] [[DBMS|database software]] needing to carry out very large numbers of read operations. Denormalization differs from the [[unnormalized form]] in that denormalization benefits can only be fully realized on a data model that is otherwise normalized.

== Implementation ==
A [[Database normalization|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 [[Information retrieval|query]] that draws information from several relations (a ''[[Join (SQL)|join operation]]'') can be slow. If many relations are joined, it may be prohibitively slow. There are two strategies for dealing with this by denormalization:
* "DBMS support": The database management system stores redundant copies in the background, which are kept consistent by the DBMS software
* "DBA implementation": The database administrator (or designer) design around the problem by denormalizing the logical data design

=== DBMS support ===
With this approach, database administrators can keep the logical design normalized, but allow the [[database management system]] (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 ([[Microsoft SQL Server]]) or [[materialized view]]s ([[Oracle Database|Oracle]], [[PostgreSQL]]). A view may, among other factors, represent information in a format convenient for querying, and the index ensures that queries against the view are optimized physically.

=== DBA implementation ===
With this approach, a database administrator or designer has 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 ''[[Constraint satisfaction|constraints]]'', that specify how the redundant copies of information must be kept synchronized, which may easily make the de-normalization procedure pointless. It is the increase in logical [[Complexity of constraint satisfaction|complexity]] of the database design and the added complexity of the additional constraints that make this approach hazardous. Moreover, constraints introduce a [[trade-off]], speeding up reads (<code>SELECT</code> in SQL) while slowing down writes (<code>INSERT</code>, <code>UPDATE</code>, and <code>DELETE</code>). This means a denormalized database under heavy write load may offer ''worse'' performance than its functionally equivalent normalized counterpart.

== Denormalization versus not normalized data ==
A denormalized data model is not the same as a data model that has not been normalized, and 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 dependency|join dependencies]] and [[Multivalued dependency|multi-valued dependencies]] are handled appropriately.

Examples of denormalization techniques include:
* "Storing" the count of the "many" elements in a [[One-to-many (data model)|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
* [[Star schema]]s, which are also known as fact-dimension models and have been extended to [[snowflake schema]]s
* Prebuilt summarization or [[OLAP cube]]s

With the continued dramatic increase in all three of storage, processing power and bandwidth, on all levels, denormalization in databases has moved from being an unusual or extension technique, to the commonplace, or even the norm.{{when|date=June 2024}} For example, one specific downside of denormalization was, simply, that it "uses more storage" (that is to say, literally more columns in a database). With the exception of truly enormous systems, increased storage requirements is considered a relatively small problem in the 2020s.

==See also==
* [[Cache (computing)]]
* [[Database normalization|Normalization]]
* [[Scalability]]

==References==
{{Reflist}}

{{Database normalization}}