Question 89 - CBDA discussion

Database normalization is the process of organizing the data in a database to reduce redundancy and improve integrity, consistency, and performance1.Database normalization rules are based on the concept of normal forms, which are levels of database design that meet certain criteria2.One of the most common normal forms is the third normal form (3NF), which states that a table should not have any transitive dependencies, meaning that a non-key attribute should not depend on another non-key attribute3. In the CustomerOrder entity, the set of attributes that will need to be normalized to avoid redundancies are ProductName and ProductQuantity, as they are non-key attributes that depend on another non-key attribute, Orderld. This means that the same product information may be repeated for different orders, which could lead to data inconsistency, duplication, or update anomalies. To normalize this set of attributes, a separate table should be created for the OrderDetails entity, which would have Orderld, ProductName, and ProductQuantity as its attributes, and Orderld and ProductName as its composite primary key.

The other sets of attributes do not need to be normalized to avoid redundancies, as they do not violate the 3NF. CustomerPhone and ProductName are non-key attributes that depend on the primary key, Customerld and Orderld respectively, which is allowed by the 3NF. Orderld and ProductName are part of the composite primary key of the OrderDetails entity, which is also allowed by the 3NF.Customerld and OrderDate are both primary keys of the Customer and Order entities respectively, which are also allowed by the 3NF.