Hello sirs, my name is , it has come to my attention that there are some misconceptions about the value in normalizing your database. I wanted to write this correspondence to address any concerns that you may have about flexibility while entering your data into the system.
This letter is to assure you and the other members of your executive board that you will have some flexibility within your E-R Model. I would like to introduce you to the concept of normalization. Normalization is used to control or reduce the amount of data redundancy and help avoid inconsistent data in your E-R Model.There are some benefits to normalization one of them Is the prevention of modification anomalies In the data. Anomalies can lead to the loss of critical data In your E-R Model; normalization will help organize your data, which will prevent redundancy In your E-R Model.
Normalization also manuals and establishes the Integrity of your data tables and should eliminate inconsistencies In your data dependencies. As with almost everything in business and life there are some pros and cons for normalization. One pro to normalization is that a well- normalized database is faster at accessing and writing data to your E-R Model.The normalization causes relational inconsistencies and this means that there would be no redundancy in your Model.
Another pro is also related to performance, a fully normalized expression of a data model is compacted data in terms of the bytes per unit of information, and this would help with performance as well. Some of the cons are that normalization requires some discipline in keeping your data well Indexed. Normalization also requires skill in providing functional views of your data so that consumers can comprehend the ALTO applications, and this can be expensive.I mentioned data redundancy and I would Like to explain what It Is. Data redundancy happens in a DB'S that has fields, which are repeated in two or more tables. This could lead to data anomalies and some corruption in the DB'S and should be avoided.
Normalization would prevent the redundancy in turn making the best possible use of storage. If the principals of normalization are followed correctly you will have a design that is very flexible, this would allow the model to be extended when there is a need for new attributes, relationships and entity sets. All of this should save space in your DB'S.There were also questions about how I arrived at INFO or three normal forms, I will explain. In the first normal form or INFO the table must be two dimensional with rows and columns. The rows will contain data that Is relevant to one thing or a portion of that thing, each column has data for a single attribute or what Is being described, and each cell of the table must be single valued.
All of the column entries must be of the same kind, each column must have a unique name, no two rows are to be identical, and the orders doesn't matter in the rows or dependent on the entire key, and the table must be in INFO.Third Normal Form or INFO, the table must have no transitive dependencies and it must be in the INFO. I hope this explanation helps you to better understand the normalization process and how it is beneficial to your DB'S.
