RelationalDBDesign
SiteMap
Database Analysis
Database Design
Extended DB Features
Oracle SQL Extensions
Normal Forms
«Prev
Next»
Data Analysis
Relational Constraints
DB Life Cycle
Relational Notation
Database Notation
Table Characteristics
Table Column Rules
Table Row Rules
Columns Entity Attributes
Calculate Domain Types
Database Null Values
Key Column Descriptors
Primary Key
Surrogate Keys
Concatenated Keys
Primary Foreign Key
Defining Foreign Keys
Referential Integrity
Relational Constructs Conclusion
Normal Forms
Reduce Data Redundancy
Normalization Defined
Normalization Objective
First Normal Form
Achieving First Normal
First NF Limitations
Second Normal Form
Define Functional Dependencies
Identify Functional Dependencies
Achieving 2ND Normal Form
Second NF Limitations
DB Normalization Conclusion
Normalization - Quiz
Third Normal Form
2NF Limitations
Transitive Dependencies
Eliminate Dependencies
Achieve Third Normal Form
1st, 2nd, 3rd NF
Codds Twelve Criteria
(BCNF) Four Important Rules
Codds Twelve Rules
Boyce Codd Normal Form
Denormalizing Tables
Joins, User Views
Permissions Design Role
SQL Joining Tables
Table Join Explanation
Create Equi Join
Permissions Requirements Analysis
SQL Inner Join
Physical Design
Database Clustering
Database Partitioning
Horizontal Partition
Disadvantages Horizontal Partitioning
DB Vertical Partitioning
Disadvantages Vertical Partitioning
Use SQL to Build DB
SQL Commands to Create Table
DB Design Mistakes
Business Objects Rules
Common Mistakes
Primary Foreign Key Mistakes
Achieving First Normal - Exercise
Achieve First Normal Form: (project exercise 2)
Objective:
Alter the given database table so that it is in first normal form.
Exercise Scoring
This exercise is worth a total of 15 points. You will receive up to five points for correctly representing the original table in
relational notation
, up to five additional points for normalizing the table, and up to five additional points for representing the results in relational notation.
Background/overview
The ER diagram you developed in the first course in this series was the foundation for a database tracking Stories on CD customers and orders. The other side of the equation is where Stories on CD purchases the CDs it sells in the first place.
At first the company only purchased CDs from a single distributor. As their client base grew, Stories on CD expanded its offerings and began to buy CDs from more than one distributor.
In some cases, the same CD is available from multiple distributors.
The company's owners sketched a prototype table to store information about CDs and which distributors they were available from. The image is displayed below.
Table consisting of columns where data redundancy has to be reduced
Your job is to take the information given to you and incorporate it into the database design.
Instructions
Represent the table from the previous graphic in relational notation, identify why the table is not in 1NF, normalize it to 1NF, and represent the resulting tables in relational notation.
Submitting your exercise
Type or paste the normalized relations into the text box below, then click
Submit
to submit the exercise and view the results page.
Submit