Lowe's Inventory Information System Database Normalization As a database grows in size and complexity, it is essential that order and organization are maintained to control these complexities and minimize errors and redundancy in the associated data. This objective is managed by a process called normalization. Normalization allows us to design our relational database tables so that they "(1) contain all the data necessary for the purposes the database is intended to serve, (2) have as little redundancy as possible, (3) accommodate multiple values ​​for types of data that require them, (4) enable efficient updates of data in the database, and (5) avoid the danger of losing data unknowingly (Wyllys, RE, 2002).” .As a prelude to normalization, the database modeler researches the company and the current database used to determine the requirements for the new database. Table elements and relationships are determined, and candidate keys for the tables are reviewed and established. The database normalization process then begins. Databases can achieve various degrees of normalization classified as 1NF, 2NF, 3NF, 4NF, 5NF and BCNF, however for convenience and to stay with Lowe's inventory database layout, only the first through third will address the normal modules or 1NF – 3NF. First, you need to find a balance between data accessibility for performance and maintenance and data redundancy concerns. To achieve this and normalize the Lowe's database, the supply and retail sides of the database were combined and the tables were set to first normal form. In early normal form, tables were formatted to ensure that the data within them was atomic, i.e. ensuring that it was in its simplest form and had no repeating groups. A chained PK characterizes tables in 1NF, and these tables can have partial and transitive dependencies. Decomposing from this point helps eliminate redundancy as the modeler works toward a defined goal based on business rules and individual needs. The tables were subsequently moved to second normal form, again subjected to an overhaul in which efforts were made to reduce the amount of redundant data by extracting it and placing it in new tables. Here, each key component is written on a separate line, with the original key written on the last line. All dependent attributes then follow their respective perspective keys. This process is used to eliminate partial dependencies that are not allowed in 2NF. Finally, the tables were set up in third normal form ensuring that no non-identifying attributes depended on other non-identifying attributes.