- Normalized databases have a design that reflects the true dependencies between tracked quantities, allowing quick updates to data with little risk of introducing inconsistencies.
- Instead of attempting to lump all information into one table, data is spread out logically into many tables.
- Normalizing the data is decomposing a single relation into a set of smaller relations which satisfy the constraints of the original relation.
- Redundancy can be solved by decomposing the tables. However certain new problems are caused by decomposition.
- Normalization helps us to make a conscious decision to avoid redundancy keeping the pros and cons in mind.
- One can only describe a database as having a normal form if the relationships between quantities have been rigorously defined.
- It is possible to use set theory to express this knowledge once a problem domain has been fully understood, but most database designers model the relationships in terms of an “idealized schema”. (The mathematical support came back into play in proofs regarding the process of transforming from one form to another.)
- The transformation of conceptual model to computer representation format is known as Normalization.
Advertisement
