Scribd
Upload
23 views2 pages

Week 4 Assignment 1

The document defines key concepts related to database design and normalization. It discusses update operations, redundant data, anomalies, functional dependencies, normal forms, denormalization, and the purpose of designer-added entities. Specifically, it defines insertion, deletion, and modification operations, and anomalies like insertion, deletion, and modification that can occur due to redundant data and denormalized tables. It also explains the concepts of functional dependency, various normal forms like 1NF, 2NF, and 3NF, and how denormalization can improve query performance by reducing joins.

Uploaded by

evansmkenya254
Copyright
© © All Rights Reserved
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
23 views2 pages

Week 4 Assignment 1

The document defines key concepts related to database design and normalization. It discusses update operations, redundant data, anomalies, functional dependencies, normal forms, denormalization, and the purpose of designer-added entities. Specifically, it defines insertion, deletion, and modification operations, and anomalies like insertion, deletion, and modification that can occur due to redundant data and denormalized tables. It also explains the concepts of functional dependency, various normal forms like 1NF, 2NF, and 3NF, and how denormalization can improve query performance by reducing joins.

Uploaded by

evansmkenya254
Copyright
© © All Rights Reserved
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/ 2

Key Concepts Exercise

1. Update operations:

 Insertion: Is used when we want to add new records to a database table,

 Deletion: Is used to remove records from a table in a database.

 Modification (update): this operation is used to change or update data that already

exists in a database.

2. Redundant data: this refers to duplicated data within a database. It can lead to

inconsistencies, increased storage requirements, and update anomalies.

3. Insertion anomaly: It occurs in a database when you cannot add certain types of data

without adding additional, unrelated data. This is because of denormalized tables within a

database.

4. Deletion anomaly: This typically happens in denormalized tables where information is

duplicated, and the deletion of one instance of the data leads to the unintentional loss of

similar data in other places.

5. Modification anomaly: Happens when updating data in a database results in

inconsistencies or inaccuracies because the update is not properly propagated to all

relevant rows or tables. This is more common in denormalized databases.

6. Functional dependency: this a relationship between two sets of attributes within a

database such that one set of attributes determines values of the other set of attributes.

7. Partial Functional Dependency happens when an attribute in a table is only dependent on

a portion of the candidate key rather than the entire key.

8. Full key functional dependency: Refers to a situation where all non-key attributes in a

database table depend on the entire primary key and not just a portion of it.
9. A transitive functional dependency occurs when an attribute depends on another attribute

through a chain of functional dependencies.

10. When a relation consists of one atomic value, it is called to be in 1 normal form (or 1NF)

in DBMS. In other words, 1NF indicates that a table's attribute will not be allowed to

hold many values; instead, it will only be able to hold a single value.

11. Second Normal Form (2NF): is a property of a relational database table that requires it to

be in 1NF and also ensures that no partial functional dependencies exist. In other words,

all non-key attributes must be functionally dependent on the entire primary key.

12. The Third Normal Form (3NF) is a characteristic of a relational database table that

mandates the table to satisfy the requirements of 2NF, and also ensures that there are no

functional dependencies that exist between non-key attributes that are transitive. This

means that non-key attributes should not depend on other non-key attributes.

13. Denormalization is the process of intentionally introducing redundancy into a database by

combining tables and storing redundant data in order to improve query performance. It is

typically done to reduce the number of joins required for complex queries.

14. The purpose of designer-added entities, tables, and keys in a database design is to

improve data accuracy, reduce redundancy, and ensure data integrity. These additions

help in organizing and structuring data in a way that reflects the real-world relationships

between entities and their attributes.

You might also like