:::: MENU ::::

Is normalization always required in database design

  • Apr 21 / 2009
  • 0
Data Modeling and Database Design, dbDigger, Performance Tunning and Optimization

Is normalization always required in database design

Normalization is an important aspect of database design. It removes redundancy and ensures relational integrity of database. Most of OLTP databases are designed up to 3rd normal form. It is important to understand that all database designs do not require normalization as it is commonly implemented till third normal form.
OLTP databases or some times called production databases make more use of normalization than OLAP or data ware house databases. Benefits of normalized database cost processing power to resolve joins and relations.
For this reason in data ware house modeling, normalization is avoided. Due to large amount of data data ware housing architects are conscious of processing time of their scripts and reports. So they prefer to consume disk resources through redundancy in data but do not afford to use joins in their scripts because joins in such large amount of data would slow down the query processing.
So we can say that use of normalization depends upon amount of data, type of database and being used hardware resources.
More levels of normalization used more tables will be created and as a result more joins will be used.

Consult us to explore the Databases. Contact us