The document discusses database normalization, a technique aimed at minimizing data redundancy and preventing anomalies through structured rules known as normal forms. It outlines the three normal forms (1NF, 2NF, and 3NF) and their requirements, emphasizing the importance of primary keys, such as the National Identity Card Number (NICN), in uniquely identifying table rows. Additionally, it highlights the concept of functional and partial dependencies within database management.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
15 views4 pages
Assaiment
The document discusses database normalization, a technique aimed at minimizing data redundancy and preventing anomalies through structured rules known as normal forms. It outlines the three normal forms (1NF, 2NF, and 3NF) and their requirements, emphasizing the importance of primary keys, such as the National Identity Card Number (NICN), in uniquely identifying table rows. Additionally, it highlights the concept of functional and partial dependencies within database management.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4
:- DATABASE MANAGEMENT 1
:- H7DX 04
:- H7DX 04/AS/02
:- M. Tharuka Navod Sudarshana
:- 200718001972 :- Colombo Answer
1. Normalization is a technique used in database design to
minimize data redundancy and prevent data anomalies. It involves structuring a database in line with certain rules or 'normal forms' that optimize the storage and accessibility of data. The process enhances the efficiency and scalability of databases, which play a crucial role in business operations and decision making.
2. First normal form (1NF). This is the "basic" level of database
normalization, and it generally corresponds to the definition of any database, namely:
It contains two-dimensional tables with rows and columns.
Each column corresponds to a sub object or an attribute of the object represented by the entire table. Each row represents a unique instance of that sub object or attribute and must be different in some way from any other row (that is, no duplicate rows are possible). All entries in any column must be of the same kind.
Second normal form (2NF). At this level of normalization,
each column in a table that is not a determiner of the contents of another column must itself be a function of the other columns in the table. The column labelled National Identity Card Number is considered a primary key because it is a column that uniquely identifies the rows in that table, and it meets the other accepted requirements in standard database management schema: It does not have NULL values and its values won't change.
Third normal form (3NF). At the second normal form,
modifications are still possible because a change to one row in a table may affect data that refers to this information from another table. Extensions of basic normal forms include the domain/key normalized form, in which a key uniquely identifies each row in a table. 3. 1st Normal Form. 4. The NICN remains unique to the employee. Therefore, the primary key should be NICN. 5. Fully functional dependencies :- (NICN, Contract No) → Hours, Employee Name, Company ID, Company Location. Partial dependencies :- NICN → Employee Name.