What is database normalization?
The underlying ideas in normalization are simple enough . Through normalization we want to design for our relational database a set of files that -
(1) contain all the data necessary for the purposes that the database is to serve.
(2) have as little redundancy as possible
(3) accommodate multiple values for types of data that requires them
(4) permit efficient updates of the data in the database, and
(5) avoid the danger of losing data unknowingly.
What are Database Anomalies?
Insertion Anomaly, Deletion anomaly and Update anomaly
Rules or steps for Normalization
Rule 1: Eliminate Repeating Groups. Make a separate table for each set of related attributes, and give each table a primary key.
Rule 2: Eliminate Redundant Data. If an attribute depends on only part of a multi-valued key, remove it to a separate table.
Rule 3: Eliminate columns not dependent on key. If attributes do not contribute to a description of the key, remove them to a separate table.
Rule 4: Isolate independent multiple relationships. No table may contain two or more 1:n (one-to-many) or n:m (many-to-many) relationships that are not directly related.
No comments:
Post a Comment