Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
13 Cards in this Set
- Front
- Back
Potential problems of poor database design |
- Data redundancy: Repetition of data in the same columns. - Data discrepancy: Conflicting details (eg. Who proper album composer is?) |
|
Database design should always conform to _____ |
business rules or logical assumptions. |
|
When creating tables, attributes referencing objects must be _____ |
unique |
|
"0..*" and "1..1" are ____ |
participation multiplicity |
|
{PK} |
Indicates attribute as Primary Key. |
|
Primary Key |
An attribute that uniquely identifies a tuple. |
|
Foreign Key |
An attribute present in one table, that is the Primary Key of another table. |
|
{FK} |
Indicates attribute is a Foreign Key |
|
Good database design must be capable of ____ in order to adapt to dynamic DB requirements |
extensions |
|
Typical output of Conceptual level design |
ER Diagram |
|
Typical output of Logical level design |
Relation Diagram |
|
Typical out of Physical level design |
Raw scripts that state names and constraints or GUI based table construction. |
|
Design styles are usually either ___ or ___ |
Top-down or Bottom-up |