Database Management Systems & Relational Data Modeling

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/29

flashcard set

Earn XP

Description and Tags

Vocabulary practice flashcards covering basic terminology, models, keys, integrity constraints, and normalization concepts from lecture notes on database management systems.

Last updated 2:33 PM on 9/24/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

30 Terms

1
New cards

Update Anomaly

An issue in computerized file-based systems where updating a single customer's address requires updating multiple entries.

2
New cards

Insertion Anomaly

An issue in file-based systems where you cannot insert information about a product until someone has purchased at least one unit of it.

3
New cards

Deletion Anomaly

An issue in file-based systems where removing a customer record causes the loss of product information if that customer was the only one who purchased the product.

4
New cards

Hierarchical Database Model

A database model based on parent-child relationships (1:M) where each record is linked to all of its child records.

5
New cards

Network Database Model

A database model created to improve on the hierarchical model by allowing records to have more than one parent and enabling data access from multiple points.

6
New cards

Relational Database Model

A model represented physically as a set of relations or tables storing data, where queries do not need to be known at design time and SQL specifies 'what' without 'how'.

7
New cards

Relation

A named two-dimensional grid or matrix of intersecting rows and columns that represents a set of tuples holding data about a set of objects.

8
New cards

Tuple

A row in a relational table, with each cell consisting of specific values for a particular variable or attribute.

9
New cards

Entity

A person, place, object, event, or concept in the user environment about which data is collected and stored.

10
New cards

Entity Type

A collection of entities that share common properties or characteristics.

11
New cards

Entity Instance

A single occurrence of an entity type.

12
New cards

Simple Attribute

An attribute that cannot be broken down into smaller components.

13
New cards

Composite Attribute

An attribute that can be broken down into its component parts.

14
New cards

Single-valued Attribute

An attribute that holds a single value for a given entity instance.

15
New cards

Multi-valued Attribute

An attribute that may take on more than one value for a given entity instance.

16
New cards

Derived Attribute

An attribute whose value can be derived from related attribute values.

17
New cards

Unary Relationship

A relationship of degree 1, also referred to as a recursive relationship or 'Bill of Materials'.

18
New cards

Degree of a Relationship

The number of entity types that participate in a specific relationship.

19
New cards

Cardinality

Specifies how many instances of one entity can (or must) be associated with each instance of another entity.

20
New cards

Associative Entity Type

An entity that associates the instances of one or more entity types and contains attributes that are peculiar to the relationship between those entity instances.

21
New cards

Superkey

An attribute or combination of attributes that uniquely identifies each row in a table.

22
New cards

Candidate Key

A minimal, irreducible superkey.

23
New cards

Primary Key

A candidate key selected to uniquely identify rows in a table; it cannot contain NULL entries.

24
New cards

Foreign Key

An attribute or combination of attributes in one table whose values must either match the primary key in another table or be NULL.

25
New cards

Secondary Key

An attribute or combination of attributes used for data retrieval.

26
New cards

Entity Integrity

An integrity rule stating that every relation has a unique primary key, and the data values for all attributes in the primary key are not NULL.

27
New cards

Referential Integrity

An integrity rule stating that every non-NULL foreign key must reference an existing primary key value.

28
New cards

Normalization

A process first developed by E.F. Codd for evaluating and decomposing table structures to minimize data redundancies and reduce data anomalies.

29
New cards

Well-Structured Relation

A relation containing minimal data redundancy that allows users to insert, delete, and update rows without causing data inconsistencies.

30
New cards

First Normal Form (1NF)

The state of a relation in which all attribute values are atomic and it contains no multi-valued attributes.