Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
The concept of database normalization, which is a portion of the relational database theory that allows the database administrator to visualize the design of the database. the main goal of database normalization, which is to remove data redundancies because it allows the tables within the database to be consistently and correctly modified. The document also discusses the requirements for a table to be in the 1NF, 2NF, and 3NF, and guidelines that must be followed for converting database tables from the lower normal forms (1NF) to the higher-level forms (3NF).
Typology: Thesis
1 / 5
This page cannot be seen from the preview
Don't miss anything!
Running head: ONLINE FOOD ORDERING DATABASE – TASK 3 1 Online Food Ordering Database – Task 3 CPT 310 Database Systems & Management Database normalization is a portion of the relational database theory that allows the database administrator to visualize the design of the database.According to Colonel & Morris
(2019), database normalization is “a process that assigns attributes to entities so that data redundancies are reduced or eliminated” (p. 199).Ideally, normalizing a database will reduce data redundancies, which will ultimately reduce the possibility of data anomalies. The main goal of database normalization is to remove data redundancies because it allows the tables within the database to be consistently and correctly modified. Normalizing a database relies upon functional dependencies, which is defined as “a relationship between two attributes, typically between the primary key and other non-key attributes within a table” (Eng&Watt, n.d., para. 1). Determining the functional dependency between two attributes enables all non-prime attributes in a table to be reliant on a primary key, ensuring that the non-prime attributes can be identified by a single primary key (Colonel & Morris, 2019). Database normalization involves six different forms, but for this paper, only the first normal form (1NF), second normal form (2NF), and third normal form (3NF) will be discussed. Additionally, guidelines that must be followed for converting database tables from the lower normal forms (1NF) to the higher-level forms (3NF) will also be discussed. The requirements for a table to be in the 1NFare that the columns or attributes should be single-valued, the values in the columns should use the same domain, and the columns in the tables should use unique names (Colonel & Morris, 2019). That said, the order in which the data is presented does not matter. As you can see in the below tables before normalization, the first employee in the table works in sales at more than one location and causes more than one value to be assigned to that column. This violates one of the rules of the 1NF, but it can be fixed by merely creating another line in the table with the appropriate information.This can be seen below in the second table before normalization.
After Normalization Reference
Coronel, C., & Morris, S. (2019). Database systems: Design, implementation, and management (13th ed.). Boston, MA: Cengage. Eng, N., &Watt, A. (2014, October 24). Chapter 11 functional dependencies. Retrieved from https://opentextbc.ca/dbdesign01/chapter/chapter-11-functional-dependencies/
