DBMS Review Flashcards

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/77

flashcard set

Earn XP

Description and Tags

Flashcards for DBMS (Database Management Systems) review, focusing on key vocabulary and concepts from the lecture notes.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

78 Terms

1
New cards

Data

A collection of raw, unprocessed facts and figures, such as text, measurements, observations, and symbols, that holds no meaning until processed and analyzed.

2
New cards

Quantitative Data

Numerical data that can be measured and expressed in numbers, such as weight, volume, or cost.

3
New cards

Qualitative Data

Descriptive data that cannot be measured numerically, such as color, gender, or name.

4
New cards

Information

Data that has been processed, organized, and structured to provide meaning and aid in decision-making by giving context to raw data.

5
New cards

Database

An organized system or electronic platform where data is stored, making it easy to retrieve, manage, and update.

6
New cards

DBMS

A Database Management System is a software system used to manage databases, allowing users to store, retrieve, modify, and delete data efficiently.

7
New cards

File System

A traditional method of storing data in separate files manually, contrasting with the organized approach of a DBMS.

8
New cards

Data Redundancy

The drawback of file processing systems where the same data is stored in multiple files, leading to duplication and conflicting values.

9
New cards

Hierarchical Data Model

A data model where data is organized in a tree-like structure with parent-child relationships, suitable for simple, predefined paths.

10
New cards

Network Data Model

A more flexible data model than the hierarchical model, organizing data using graphs and allowing many-to-many relationships.

11
New cards

Relational Data Model

A data model where data is organized in tables with rows and columns, accessed using SQL, and widely used in systems like MySQL and Oracle.

12
New cards

Physical Level (Internal Level)

The lowest level of DBMS architecture, describing how data is stored physically in memory using low-level data structures like indexes and B+ Trees.

13
New cards

Logical Level (Conceptual Level)

The middle level of DBMS architecture, describing what data is stored and the relationships, handled by a DBA to ensure simplicity and consistency.

14
New cards

View Level (External Level)

The highest level of DBMS architecture, providing customized views to different users for security, simplicity, and personalization.

15
New cards

Instance

The data in the database at a specific moment, representing a snapshot of the database.

16
New cards

Schema

The overall design or structure of the database, which does not change frequently and includes physical, logical, and view schemas.

17
New cards

DDL (Data Definition Language)

A database language used to define the schema, including commands like CREATE, ALTER, and DROP, and defining constraints such as primary and foreign keys.

18
New cards

DML (Data Manipulation Language)

A database language used to handle data, including commands like SELECT, INSERT, UPDATE, and DELETE, with SQL being a part of DML.

19
New cards

Database Administrator (DBA)

An individual responsible for schema definition, storage and access method setup, authorization, access control, and routine maintenance of a database.

20
New cards

Tier-1 (T1) Architecture

A DBMS application architecture where all components (client, database, application) are on the same machine.

21
New cards

Tier-2 (T2) Architecture

A DBMS application architecture using a client-server structure where the client sends SQL queries to the database server.

22
New cards

Tier-3 (T3) Architecture

A three-tier architecture (Client -> App Server -> DB Server) for DBMS applications, best for web applications, providing scalability and security.

23
New cards

ER Model

A high-level data model based on a perception of a real world that consists of a collection of basic objects, called entities and of relationships among these objects.

24
New cards

Entity

A thing or object in the real world that is distinguishable from all other objects and can be uniquely identified by a primary key.

25
New cards

Weak Entity

An entity that cannot be uniquely identified by its attributes alone and depends on a strong entity for its existence.

26
New cards

Entity Set

A set of entities of the same type that share the same properties or attributes.

27
New cards

Attribute

A property or characteristic of an entity, represented by a value from its domain.

28
New cards

Simple Attribute

An attribute that cannot be divided further into subparts, such as a customer's account number.

29
New cards

Composite Attribute

An attribute that can be divided into subparts or other attributes, such as a person's name.

30
New cards

Single-Valued Attribute

An attribute that can only have one value, such as a student ID or loan-number.

31
New cards

Multi-Valued Attribute

An attribute that can have more than one value, such as a phone-number or nominee-name.

32
New cards

Derived Attribute

An attribute whose value can be derived from the value of other related attributes, such as age.

33
New cards

NULL Value

A value that an attribute takes when an entity does not have a value for it, indicating 'not applicable' or 'unknown'.

34
New cards

Relationship

An association among two or more entities, such as a person having a vehicle or a customer borrowing a loan.

35
New cards

Unary Relationship

A relationship in which only one entity participates, such as an employee manages employee.

36
New cards

Binary Relationship

A relationship in which two entities participate, such as a student taking a Course.

37
New cards

Relationship Constraints

Rules that specify the number of entities to which another entity can be associated via a relationship (mapping cardinality) and whether all entities must participate (participation constraints).

38
New cards

Specialization (in EER)

The process of dividing a single entity set into multiple sub-entity sets based on specific attributes or roles.

39
New cards

Generalization (in EER)

The process of combining two or more entity sets that share common features into a higher-level entity set.

40
New cards

Attribute Inheritance (in EER)

Lower-level entities (subclasses) inherit attributes of the higher-level entities (superclass).

41
New cards

Aggregation (in EER)

Abstraction concept used when a relationship acts as an entity itself.

42
New cards

Relation (Table)

A table with rows and columns, representing a specific type of entity

43
New cards

Tuple

A row in a table, representing a single data point or record.

44
New cards

Attribute

A column in a table, representing a property or characteristic of the entity.

45
New cards

Relation Schema

Describes the structure of a table: its name and its attributes.

46
New cards

Degree

Number of attributes in a relation (i.e., number of columns).

47
New cards

Cardinality

Number of tuples (i.e., number of rows) in a relation.

48
New cards

Super Key

Any combination of attributes that can uniquely identify a tuple.

49
New cards

Candidate Key

Minimal super key. Contains no redundant attributes.

50
New cards

Primary Key (PK)

A chosen candidate key. Must be unique and not NULL.

51
New cards

Foreign Key (FK)

Used to establish a relationship between two tables. References primary key of another table.

52
New cards

Domain Constraint

Defines the data type and range of values for an attribute.

53
New cards

Entity Integrity Constraint

Every relation must have a primary key. No attribute of the primary key can be NULL.

54
New cards

Referential Integrity Constraint

Maintains valid references between tables. A FK must refer to an existing PK in another table or be NULL. Ensures no orphan records in child table.

55
New cards

Multivalued Attributes

Attributes that can hold multiple values (e.g., phone numbers). Create a new table for each multivalued attribute.

56
New cards

Relational Algebra

A procedural query language used to query relational database

57
New cards

Tuple Relational Calculus

Queries are expressed using variables that range over tuples.

58
New cards

Domain Relational Calculus

Queries are expressed using variables that range over attributes (domains).

59
New cards

Embedded SQL

SQL code embedded within a host programming language (like C, Java, etc.).

60
New cards

PL/SQL (Procedural Language/SQL)

Oracle’s procedural extension to SQL, allowing developers to write complex queries and control structures (loops, conditions) in SQL.

61
New cards

Query Processing

The process of transforming an SQL query into an efficient execution plan.

62
New cards

Query Optimization

Involves choosing the most efficient way to execute a query.

63
New cards

Normalizaiton

Normalization is the process of structuring a relational database to reduce data redundancy and improve data integrity.

64
New cards

Functional Dependency

A functional dependency expresses a relationship where one set of attributes uniquely determines another set.

65
New cards

Transaction

A transaction is a logical unit of work that consists of one or more SQL operations.

66
New cards

ACID Properities

ACID properties are essential to guarantee reliable processing in a database system. They include: Atomicity, Consistency, Isolation, Durability

67
New cards

Serializability

Serializability ensures the consistency of a database when multiple transactions are executed concurrently.

68
New cards

Concurrency Control

Goal: To allow multiple transactions to execute safely and efficiently without interfering with eachother, ensuring isolation and consistency.

69
New cards

Database Recovery

Recovery ensures that the database is in a consistent state after a failure. It brings the DB back to the last consistent state.

70
New cards

Data Storage

Data storage refers to how and where the data is physically stored — in files, blocks, or pages — usually on disks (like HDD, SSD).

71
New cards

Index

An index is like a book index — it helps you find data faster by pointing to its location.

72
New cards

Hashing

Hashing is a technique used in DBMS to quickly locate data in a table using a hash function.

73
New cards

CAP Theorem

The CAP Theorem (also called Brewer's Theorem) is a principle that applies to distributed databases that states that: A distributed system can guarantee only two out of the following three properties at the same time: 1. Consistency (C) 2. Availability (A) 3. Partition Tolerance (P)

74
New cards

NoSQL

NoSQL Database is a non-relational Data Management System, that does not require a fixed schema.

75
New cards

MongoDB

MongoDB is a document-oriented NoSQL database used for high volume data storage.

76
New cards

Apache Cassandra

Apache Cassandra is a distributed, wide-column NoSQL database designed for handling large volumes of data across many servers with high availability and no single point of failure.

77
New cards

Apache HBase

Apache HBase is a distributed, column-oriented NoSQL database built on top of Hadoop HDFS. It's modeled after Google’s Bigtable as well and is optimized for random, real-time read/write access to big data.

78
New cards

Redis

Redis (REmote DIctionary Server) is an in-memory key-value data store known for ultra-fast performance.