Logical Design Flashcards

1
Q

Goal of logical design in relational databases

A

Convert E/R schema into a relational schema that is efficient and maintains the original data integrity and relationships

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the two main phases of logical design?

A
  1. Restructuring E/R schema
  2. Translating to relational
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

How are genrealization hierarchies handled in logical design?

A

Collapsing hierarchies upward, downward, or reifying them as relationships

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What happens to multivalued attributes during restructuring?

A

They are either replaced with single-valued attributes or converted into a new table

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

How are 1:N relationships translated into relational tables?

A

Add primary key of one side as foreign key in many side

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

How are N:M relationships represented in the relational model?

A

Using a bridge table containing the primary keys of the related entities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is a recursive relationship?

A

Entity references itself, implemented bby adding a foreign key referencing the same table

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What criteria are used to select a primary identifier?

A
  1. Simplicity
  2. Minmal null values
  3. frequent usage in operations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

How would you handle a multivalued attribute like “PhoneNumbers”?

A

Replace it with a separate table containing PhoneNumber and a foreign key referencing the original entity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

How is generalization with overlapping coverage handled?

A

Reifying it as a relationship to avoid redundancy and manage specific attributes for subtypes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Principle of “Keep togetherwhat is used together”

A

Design tbales to optimize for frequent operations, minimizing the need for complex joins

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Why is documentation important for logical design?

A

Ensure all constraints and relationships are clear, aiding in maintainability and schema evolution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly