| Composite primary key | Consists of the primary key fields from the two intersecting relations.
(See page(s) 280)
|
 |
 |
 |
Data dictionary
| Contains the logical structure for the information in a database.
(See page(s) 286)
|
 |
 |
 |
| Database | A collection of information that you organize and access according to the logical structure of that information.
(See page(s) 272)
|
 |
 |
 |
| Database management system (DBMS) | Helps you specify the logical organization for a database and access and use the information within the database.
(See page(s) 286)
|
 |
 |
 |
| Entity class | A concept typically people, places, or things about which you wish to store information and that you can identify with a unique key (called the primary key).
(See page(s) 274)
|
 |
 |
 |
| Entity-relationship (E-R) diagram | A graphic method of representing entity classes and their relationships.
(See page(s) 275)
|
 |
 |
 |
| Foreign key | A primary key of one file (relation) that appears in another file (relation).
(See page(s) 280)
|
 |
 |
 |
| Instance | An occurrence of an entity class that can be uniquely described.
(See page(s) 274)
|
 |
 |
 |
| Intersection relation (composite relation) | A relation you create to eliminate a many-to-many relationship.
(See page(s) 280)
|
 |
 |
 |
| Normalization | A process of assuring that a relational database structure can be implemented as a series of two-dimensional relations.
(See page(s) 280)
|
 |
 |
 |
| Primary key | A field (or group of fields in some cases) that uniquely describes each record.
(See page(s) 274)
|
 |
 |
 |
| Relational database | Uses a series of logically related two-dimensional tables or files to store information in the form of a database.
(See page(s) 272)
|