Professional Documents
Culture Documents
Is Characterized by A Large
Is Characterized by A Large
There are two primary advantages of having a highly normalized data schema:
1.Increased consistency. Information is stored in one place and one place only, reducing the possibility of inconsistent data.
2.Easier object-to-data mapping. Highly-normalized data schemas in general are closer conceptually to object-oriented schemas because the object-oriented goals of
promoting high cohesion and loose coupling between classes results in similar solutions (at least from a data point of view).
You typically want to have highly normalized operational data stores (ODSs) and data warehouses (DWs).
The primary disadvantage of normalization is slower reporting performance. You will want to have a denormalized schema to support reporting, particularly in data marts.
Table 1 summarizes the three most common forms of normalization ( First normal form (1NF), Second normal form (2NF), and Third normal form (3NF)) describing how to put entity
types into a series of increasing levels of normalization. Higher levels of data normalization are beyond the scope of this article. With respect to terminology, a data schema is
considered to be at the level of normalization of its least normalized entity type. For example, if all of your entity types are at second normal form (2NF) or higher then we say that
your data schema is at 2NF.
Level Rule
https://www.capterra.com/business-intelligence-software/#infographic