Definition: Normalization is the process of organizing tables, so that when you are using the database it will be easy to use and also intended to work as it is supposed to work. This will help to duplicate the information that you will put into the database and also will result in additional tables that are needed to normalize the database so that it will work and process the information as intended. The purpose of normalization is to help create a database so that it will work as intended and increase the duplication of the data that will be put into the table. Without normalization the database will not work effectively, nor will it have the table increased to a normal standard that is understandable. It is a refinement of information that will help identify the objects and the attribute within the database that will help the relationships, make definitions for the requirements.
1st Normal form
" Every column in the database must be normal and unique.
" You will need to separate the tables to show the related data.
" Each table has to have identification with their primary keys present.
" You cannot have any duplicate information inside of the tables.
" You cannot have any null values in the table's rows and columns.
" You cannot have any fields that are motivated, nor any rows.
2nd Normal form
" There should be no functional dependencies on the primary key.
" The table can contain candidate key.
" No non-prime attributes have dependencies on the candidate keys.
3rd Normal form
" The database will build on the 1st and 2nd normal form.
" All columns will have referenced data and be non- dependent on the primary key.
" Data not dependent on the primary key should be deleted or removed from the database.
" Only the foreign keys should be used to reference the information for another table.
" You cannot use any columns from the parent table, and should exist in the referenced table that will be used for the database.
3rd Normal form reduces inserts by not adding entries or attributes that aren't dependent on the primary key. It updates the anomalies by, changing the information in that database and altering the information so that it fits into the relation of the database. Last, it will delete anomalies by, deleting unwanted rows in the database that aren't needed to make it a 3rd normal form. This is how 3rd normal form reduces inserts, updates and deletes it anomalies.
Created on February 22, 2015 by Lionel Sharpe || Professor Thomas-Moore Pizon
Form (rr15a) Code:3301627005-GA
Form (rr15b) Code:3301627006-NJ