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;
16 Cards in this Set
- Front
- Back
Phases of Relational Database Design
|
1) Analysis
2)Design 3)Implementation |
|
Client Requirements
|
Information collected from client to create sound database design
|
|
Business Rules
|
Procedures and policies of company that would affect input of data into database
|
|
TABLE
|
Set of data elements that are organized using a model of columns and rows.
|
|
DATA FIELD
|
Column in a database
|
|
DATA FIELD
|
Also called an "attribute"
|
|
KEY
|
Data field that ensures each record is uniquely identified
|
|
Candidate Key
|
A field or combination of fields that uniquely identify each record in a table.
|
|
Primary Key
|
A field that would always accept unique value and never a blank.
|
|
Foreign Key
|
A field that matches the primary key column of another table
|
|
Null Value
|
Value used to indicate the absence of data in a given field
|
|
RELATIONSHIP
|
Method used to link two tables based on presence of a common field that is found in both tables
|
|
CARDINALITY
|
Relationship among tables based on the number of rows in one table related to the number of rows in another table.
|
|
Bridge Table
|
Tables used to avoid many-to-many relationships in database.
|
|
Entity Relationship Diagram
|
Graphical representation of the design of the database.
|
|
Data Anomaly
|
Data inconsistency in table when rows are inserted, updated, or deleted.
|