Organize data into multiple related tables

Increase data redundancy

Slow down data retrieval

Delete all data

Deleting pieces of information

Repeating data for every new row

Changing a particular data

Inserting data into the wrong table

To make data manipulation easier

To prevent data redundancy

To allow multiple values in a column

To make data retrieval slower

Considered as bad DB design

Data is easily extended

Data is well-organized

Data retrieval is faster

Ensuring data is easily extended and retrieved

Increasing data redundancy

Creating multiple unrelated tables

Deleting all data

Allow data to be stored in any format

Ensure data integrity

Allow data duplication

Increase data redundancy

Each column should have a unique name

Each column should contain atomic values

Each column should contain multiple values

Data order in the table matters

First and Second Normal Form

Transitive dependency

Composite Key

Partial dependency

A key that is easy to guess

A key that is not unique

A key that is not needed

A key made up of multiple columns

CourseID

Course Fee

Order no

StudentID

Update/Modification anomaly

Deletion anomaly

Insertion anomaly

Data Integrity anomaly

A way to speed up data retrieval

A method to secure data

A technique of organizing data

The repetition of similar data at multiple places

Allow data to be stored in any order

Ensure data is easily extended

Remove partial dependency

Increase data redundancy