Normalization Process [Tables]

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

1.	Which statement best describes database normalization? Please select the best answer.
	A.	Converting an ER diagram into tables without checking their dependencies
	B.	Combining related tables to minimize the number of joins
	C.	Adding a generated primary key to every table
	D.	Organizing relations according to their keys and dependencies to reduce redundant facts and data anomalies

2.	A table stores customer details only in order-line rows. Which problems can result from combining these facts? Please select all the correct answers.
	A.	A customer's current phone number may be repeated across many order lines
	B.	Changing that phone number may require several updates, with inconsistent values if a row is missed
	C.	Queries against the table must always be slower than queries against a normalized design
	D.	Deleting a customer's final order line may remove the only stored copy of that customer's details

3.	What does the term normal form describe? Please select the best answer.
	A.	A set of conditions a relation satisfies concerning its structure or dependencies
	B.	A sample database supplied with a database management system
	C.	A guarantee that a table uses the least possible storage
	D.	A diagram notation used to display entities and relationships

4.	What does the functional dependency CustomerID → CustomerName mean? Assume the relation stores one current name per customer. Please select the best answer.
	A.	Every customer must have a different name
	B.	Rows with the same CustomerID must have the same CustomerName in every valid state of the relation
	C.	A customer's name can never change
	D.	CustomerName must also determine CustomerID

5.	What must a lossless decomposition allow you to do? Please select the best answer.
	A.	Remove every repeated value, including repeated foreign keys
	B.	Guarantee that all queries run faster
	C.	Reconstruct the original relation by joining its projections without losing tuples or introducing spurious combinations
	D.	Keep the same number of rows in every resulting table

Database Normalization Process - Quiz