RelationalDBDesign
SiteMap
Database Analysis
Database Design
Extended DB Features
Oracle SQL Extensions
Relational Constructs
«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
RDBMS Calculations
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
(BCNF) Four Important Rules
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
DB Design Considerations
Business Objects Rules
Database Column Mistakes
Database Key Constraints
Primary Foreign Key Mistakes
Referential Integrity
International DB Mistakes
Eval Relational DB
Design Mistakes Conclusion
Rules for Database Rows - Exercise
Translate entities and attributes
Objective:
Translate entities and attributes into tables with column headings.
Exercise scoring
This exercise is worth a total of two points. This exercise is auto-scored. When you have answered the question below, click the
Submit
button to receive credit for having completed the exercise and view a results page.
Background and Overview
In this exercise, you will create tables with column headings based on the entities and attributes in the ER diagram for the course project. This is the beginning of a database design that tracks orders placed with Stories on CDs.
Instructions
Below is an illustration of the ER diagram for the Stories on CD case study. Create tables with column headings for the Customer, Order, CD, Distributor, and Line Item entities on the diagram.
This image is a schema diagram of a database for "Stories on CD, Inc." It includes five entities:
CUSTOMER,
ORDER,
LINE ITEM,
CD, and
DISTRIBUTOR.
Each entity is shown with its attributes; primary keys (PK) and foreign keys (FK) are indicated.
Relationships between entities are represented with lines showing the associations. For instance, CUSTOMER is linked to ORDER indicating a relationship where a customer can have multiple orders. This schema helps in understanding how data is structured and interrelated in the database.
Submitting your Exercise
This exercise is auto-scored, which means there is nothing to submit.
When you have answered the question, click the
Submit
button to receive credit for completing the exercise and view a results page.