Logical Design, Part 2

Assuming one of the executives is not too keen on normalizing the database, discerning that the system would be too constrained and lacking flexibility while entering data. Normalization benefits the organization; organizing data establishing tables and forming relationships. In order to alter the executives thought on normalization; delivering information on the benefits and disadvantages along with the dangers of data redundancy; depicting the previous entity diagram and describing the steps necessary to reach normalization should assist in reconsidering this notion.

Normalization provides countless benefits; providing a stronger understanding of business; assuring the right data elements are assigned to the correct entities. It entails Greater application stability; the normalization process basically replicates or follows the way the organization works. Once the normalized model is structured the system will run smoothly and quicker ( Hoberman, p.136). This configuration creates a flexible structure, delivering a better understanding of the data. Yet, the most important advantage or of normalization is to reduce data redundancy and avoid inconsistent data. Each level of normalization removes a type of data redundancy from the model; quicker process, less information to update or insert, therefore making it easier to maintain ( Hoberman, p.136). On the other hand, implementing this technique necessitates skilled professionals. Users require discipline; to keep data updated and normalized

Wasted disk space is not the only danger of having data redundancy in a database. Redundant data creates database maintenance issues, anomalies or inconsistencies in data. Problems include identifying needs; updating, deleting and inserting may be difficult. Changes would have to be made to every piece of reoccurring data. The more copies of information the more confusion, the more inconsistent the data. Although there are detriments associated with data redundancy,...