RelationalDBDesign
SiteMap
Database Analysis
Database Design
Extended DB Features
Oracle SQL Extensions
Physical Design
«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
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
Vertically Partitioning Table - Quiz
Each question is worth one point. Select the best answer or answers for each question.
1.
Vertically partitioning a table creates what change to the table?
Please select the best answer.
A.
The table's rows are stored in two or more smaller tables.
B.
The table's columns are stored in two or more smaller tables, linked by the original table's primary key fields.
C.
The table's columns are combined with columns from another table.
D.
The table's rows are combined with rows from another table.
2.
Horizontally partitioning a table can result in what performance trade-offs?
Please select all the correct answers.
A.
Finding records in more than one partition is faster than if the records were in a single, larger table.
B.
Finding records in more than one partition is slower than if the records were in a single, larger table.
C.
Finding records in a single partition is faster than if the records were in a single, larger table.
D.
Finding records in a single partition is slower than if the records were in a single, larger table.
3.
Vertically partitioning a table slows down what operations?
Please select all the correct answers.
A.
Joins based on frequently joined fields
B.
Inserting new records
C.
Searching complete records
D.
Deleting records
4.
When is vertical partitioning most beneficial?
Please select the best answer.
A.
When a table has many rows but only a few columns are frequently accessed
B.
When a table has many columns but only a few are frequently accessed in queries and joins
C.
When most queries need every column in the table
D.
When the table is very small
5.
Which of the following are common reasons to vertically partition a table?
Please select all the correct answers.
A.
To reduce I/O by retrieving only needed columns
B.
To allow different indexing strategies on different column groups
C.
To isolate large or rarely used columns (e.g., BLOBs, long text)
D.
To improve performance of queries that always retrieve the entire row