Database Systems: Design, Implementation, and Management (Chapters 1–6)

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

1/90

flashcard set

Earn XP

Description and Tags

Comprehensive vocabulary practice flashcards covering fundamental and advanced database concepts, data models, relational database theory, entity relationship modeling, extended ER modeling, and table normalization from Chapters 1 through 6.

91 Terms

1
New cards

Data

Raw facts, such as a telephone number, a birth date, a customer name, or a year-to-date sales value, that have little meaning unless organized in some logical manner.

2
New cards

Information

The result of processing raw data to reveal its meaning, requiring context to reveal that meaning.

3
New cards

Metadata

Data about data, providing descriptions of data characteristics and relationships within the data.

4
New cards

Database Management System (DBMS)

A collection of programs that manages the database structure and controls access to the data stored in the database.

5
New cards

Data Inconsistency

A condition in which different and conflicting versions of the same data appear in different places.

6
New cards

Ad Hoc Query

A spur-of-the-moment question issued to a DBMS for data manipulation or retrieval.

7
New cards

Operational Database

A database designed primarily to support a company's day-to-day operations; also known as a transactional or production database.

8
New cards

Analytical Database

A database that focuses primarily on storing historical data and business metrics used exclusively for tactical or strategic decision making.

9
New cards

Online Analytical Processing (OLAP)

A set of tools that work together to provide an advanced data analysis environment for retrieving, processing, and modeling data from a data warehouse.

10
New cards

NoSQL

A new generation of database management systems that is not based on the traditional relational model, designed to handle unprecedented data volume, variety, and velocity.

11
New cards

Structural Dependence

A file system characteristic where access to a file is dependent on its own internal file structure, requiring program code changes if the file structure changes.

12
New cards

Data Independence

A condition in which changes in data storage characteristics do not affect data access or require modifications to application programs.

13
New cards

Data Redundancy

A condition in which the same data is stored unnecessarily in multiple places across an organization.

14
New cards

Data Model

A relatively simple representation, often graphical, of complex real-world data structures and problem domains.

15
New cards

Entity

A person, place, thing, concept, or event in the real-world environment about which data are to be collected and stored.

16
New cards

Attribute

A characteristic or property of an entity.

17
New cards

Constraint

A restriction placed on the data to ensure data integrity.

18
New cards

Business Rules

Precise, written descriptions of policies, procedures, or principles within a specific organization that define the characteristics and operational actions of data.

19
New cards

Segment

In the hierarchical data model, the equivalent of a file system's record type arranged in an upside-down tree structure.

20
New cards

Hadoop Distributed File System (HDFS)

A highly distributed, fault-tolerant file storage system that uses a write-once, read-many model across clusters of computers using name nodes, data nodes, and client nodes.

21
New cards

MapReduce

An open-source API that distributes data analytics processing across thousands of nodes in parallel using a Map function to divide jobs and a Reduce function to integrate results.

22
New cards

Eventual Consistency

A data consistency model in distributed NoSQL databases where updates propagate across the system over time until all data copies eventually match.

23
New cards

External Model

The end users' view of the data environment, represented by external schemas that are independent of both hardware and software.

24
New cards

Conceptual Model

A global, integrated view of the entire database representing all external views, designed to be independent of both hardware and DBMS software.

25
New cards

Internal Model

The representation of a database as seen by the DBMS, mapping the conceptual model to specific database software while remaining hardware-independent.

26
New cards

Physical Model

The lowest level of data abstraction that describes physical storage media and data access methods, dependent on both hardware and software.

27
New cards

Tuple

A single row within a relational table representing an entity occurrence in an entity set.

28
New cards

Attribute Domain

The specific range or set of allowable values defined for a particular column in a table.

29
New cards

Superkey

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

30
New cards

Candidate Key

A minimal, irreducible superkey that does not contain a subset of attributes that is itself a superkey.

31
New cards

Primary Key

A candidate key selected to uniquely identify all other attribute values in any given row, which cannot contain null entries.

32
New cards

Foreign Key (FK)

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

33
New cards

Secondary Key

An attribute or combination of attributes used strictly for data retrieval purposes.

34
New cards

Entity Integrity

The integrity rule requiring that all primary key entries be unique and that no part of a primary key may contain a null value.

35
New cards

Referential Integrity

The integrity rule requiring that every non-null foreign key value reference an existing valid primary key value in the related table.

36
New cards

Flag

A special code or dummy variable implemented to indicate the absence of a value, prevent nulls, or trigger a required response.

37
New cards

Natural Join

A relational algebra operation that links tables by selecting rows with common values in common attributes through a sequence of PRODUCT, SELECT, and PROJECT operations.

38
New cards

Left Outer Join

A relational operator that yields all rows from the left table, including those without matching values in the right table, filling unmatched right-side attributes with nulls.

39
New cards

Right Outer Join

A relational operator that yields all rows from the right table, including those without matching values in the left table, filling unmatched left-side attributes with nulls.

40
New cards

Divide

A relational algebra operator that outputs rows from a table associated with all the values found in a single-column table.

41
New cards

Data Dictionary

A system storage repository that provides a detailed accounting of all tables, attribute names, data types, formats, and metadata in a database.

42
New cards

System Catalog

A detailed system-level data dictionary that describes all objects (such as tables, views, indexes, and user accounts) within the database.

43
New cards

Unique Index

An index structure in which each index key can have only one pointer value (row) associated with it.

44
New cards

Rule Zero

Dr. E.F. Codd's foundational relational rule stating that to be considered relational, a database must use its relational facilities exclusively for management.

45
New cards

Required Attribute

An attribute that must have a value and cannot be left empty (null).

46
New cards

Optional Attribute

An attribute that does not require a value and may be left blank.

47
New cards

Composite Identifier

A primary key identifier composed of more than one attribute.

48
New cards

Composite Attribute

An attribute that can be subdivided into smaller components, such as ADDRESS into street, city, state, and zip code.

49
New cards

Simple Attribute

An attribute that cannot be subdivided into smaller components, such as age or sex.

50
New cards

Multivalued Attribute

An attribute that can have multiple values for a single entity occurrence, such as multiple colors for a car.

51
New cards

Derived Attribute

An attribute whose value is not physically stored in the database but is calculated from other stored attributes using an algorithm.

52
New cards

Connectivity

The classification label used to describe the relationship type between entities (such as 1:1, 1:M, or M:N).

53
New cards

Cardinality

A property that expresses the minimum and maximum number of entity occurrences associated with one occurrence of a related entity.

54
New cards

Weak (Non-Identifying) Relationship

A relationship in which the primary key of the related entity does not contain the primary key component of the parent entity.

55
New cards

Strong (Identifying) Relationship

A relationship that exists when the primary key of the related entity contains the primary key component of the parent entity.

56
New cards

Weak Entity

An entity that is existence-dependent on another entity and whose primary key is partially or totally derived from its parent entity.

57
New cards

Unary Relationship

A relationship that exists when an association is maintained within occurrences of a single entity set; also known as a recursive relationship.

58
New cards

Ternary Relationship

An association that involves three distinct entities simultaneously.

59
New cards

Associative Entity

A bridge or composite entity used to implement an M:N relationship, composed of the primary keys of the entities to be linked as foreign keys.

60
New cards

Extended Entity Relationship (EER) Model

The data model resulting from adding advanced semantic constructs, such as supertypes, subtypes, and clusters, to the original entity relationship model.

61
New cards

Entity Supertype

A generic entity type that contains common characteristics and attributes shared by one or more entity subtypes.

62
New cards

Entity Subtype

A specialized entity type that inherits attributes from an entity supertype and contains its own unique characteristics.

63
New cards

Specialization Hierarchy

A structural arrangement depicting higher-level supertypes and lower-level subtypes connected by 'IS-A' relationships.

64
New cards

Subtype Discriminator

An attribute in an entity supertype that determines to which entity subtype each supertype occurrence is related.

65
New cards

Disjoint Subtypes

Nonoverlapping subtypes containing unique subsets of a supertype, meaning an instance can belong to only one subtype, denoted by a 'd' in the category symbol.

66
New cards

Overlapping Subtypes

Subtypes containing nonunique subsets of a supertype, allowing a single supertype occurrence to simultaneously belong to multiple subtypes, denoted by an 'o'.

67
New cards

Partial Completeness

A specialization hierarchy constraint symbolized by a circle over a single line, indicating that some supertype occurrences do not belong to any subtype.

68
New cards

Total Completeness

A specialization hierarchy constraint symbolized by a circle over a double line, indicating that every supertype occurrence must belong to at least one subtype.

69
New cards

Specialization

The top-down process of identifying more specific entity subtypes from a higher-level entity supertype based on grouping unique characteristics.

70
New cards

Generalization

The bottom-up process of identifying a generic entity supertype from multiple lower-level entity subtypes based on grouping shared characteristics.

71
New cards

Entity Cluster

A virtual entity type used in an ERD to represent multiple interrelated entities and relationships, simplifying cluttered diagrams.

72
New cards

Natural Key

A real-world identifier familiar to end users and part of day-to-day business vocabulary, used to identify entity instances.

73
New cards

Surrogate Key

An artificial, system-assigned primary key created when no suitable natural key exists or the candidate key is too long or cumbersome.

74
New cards

Time-Variant Data

Data whose values change over time and for which a historical record of values and change dates must be retained.

75
New cards

Fan Trap

A design trap occurring when one entity is in two simultaneous 1:M relationships to other entities, creating an association between those other entities that is not accurately represented.

76
New cards

Redundant Relationship

A condition in an ERD where multiple relationship paths exist between related entities, introducing potential inconsistencies.

77
New cards

Normalization

A process for evaluating and correcting table structures to minimize data redundancies and eliminate data anomalies.

78
New cards

Functional Dependence

A state in which attribute BB is dependent on attribute AA (A→BA \rightarrow B) if each value of AA determines one and only one value of BB.

79
New cards

Determinant

Any attribute whose value determines other values within a row; the attribute on the left side of a functional dependency arrow (AA in A→BA \rightarrow B).

80
New cards

Fully Functional Dependence

A condition where attribute BB is functionally dependent on a composite key AA, but not on any subset of that composite key.

81
New cards

Partial Dependency

A functional dependency in which a nonkey attribute is dependent on only a portion of a composite primary key.

82
New cards

Transitive Dependency

A dependency that exists when a nonkey attribute determines another nonkey attribute (X→YX \rightarrow Y and Y→ZY \rightarrow Z, where XX is the primary key).

83
New cards

Repeating Group

A group of multiple entries of the same type that can exist for any single key attribute occurrence in an unnormalized record.

84
New cards

First Normal Form (1NF)

A table format characterized by defined primary keys, no repeating groups, and all attributes being functionally dependent on the primary key.

85
New cards

Second Normal Form (2NF)

The state of a table that is in 1NF and contains no partial dependencies, meaning no nonkey attribute depends on a subset of the primary key.

86
New cards

Third Normal Form (3NF)

The state of a table that is in 2NF and contains no transitive dependencies, meaning no nonkey attribute determines another nonkey attribute.

87
New cards

Boyce-Codd Normal Form (BCNF)

A special, stricter case of 3NF in which every determinant in the table is a candidate key.

88
New cards

Fourth Normal Form (4NF)

The state of a table that is in 3NF (or BCNF) and contains no multiple sets of independent multivalued dependencies.

89
New cards

Fifth Normal Form (5NF / PJNF)

Project-join normal form; the state of a table in 4NF that cannot undergo further lossless decomposition into smaller tables without losing data.

90
New cards

Denormalization

The deliberate process of converting higher normal form tables into lower normal forms to reduce join operations and increase processing speed at the expense of data redundancy.

91
New cards

Minimal Data Rule

A core data modeling principle stating that 'all that is needed is there, and all that is there is needed.'