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
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
Normalization Process - Quiz
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
1st, 2nd, 3rd NF
Achieve 3rd Normal Form
Codds Twelve Criteria
Beyond 3rd Normal Form
Boyce Codd Normal Form
Denormalizing Tables
3rd Normal Form
Joins, User Views
SQL Joining Tables
SQL Inner Join
Table Join Explanation
Create Equi Join
Business Requirements
Store View Definitions
Creating SQL Views
Permissions Design Role
Requirements Analysis
Table Joins User Views
Physical Design
Physical DB Design
Create index SQL
Drawbacks Field Indexing
Database Clustering
Data Clustering Trade-off
Database Partitioning
Horizontal Partition
Drawbacks Horizontal Partitioning
DB Vertical Partitioning
Drawbacks Vertical Partitioning
Create DB via SQL
Create Table via SQL
Use SQL to Build DB
Data Dictionary Entries
Data Dictionary
Physical Design Conclusion
DB Design Mistakes
Common Mistakes
Business Objects Rules
Database Column Mistakes
Database Key Constraints
Primary Foreign Key Mistakes
Referential Integrity
International DB Mistakes
Eval Relational DB
Design Mistakes Conclusion
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 15 self-assessed points. Compare your response with the model answer on the results page; the site does not automatically grade your answer. Award up to 5 points for the original relational notation, 5 for removing the repeating distributor slots while preserving the facts, and 5 for the resulting 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.
Original data: the numbered distributor slots list suppliers from which each CD is available. They do not identify which distributor fulfilled an order. The original dates, prices, and names are preserved.
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.