Database Management System

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/115

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

116 Terms

1
New cards

Data

One of the most valuable resources

2
New cards

Database

Organizes raw data into meaningful information

3
New cards

Database Management System

Provides tools to store, retrieve, and secure information

4
New cards

Data

Raw facts and figures, No context or meaning until processed, Can be numbers, text, images, or symbols, Example: 85, Maria, CMPE401.

5
New cards

Information

Processed or organized data that has meaning and value, Example: “Maria scored 85 in CMPE401.” Now the data has context (student, subject, grade).

6
New cards

Data

individual puzzle pieces.

7
New cards

Information

completed puzzle showing the picture.

8
New cards

Database

an organized collection of related data stored in a structured way, so it can be easily accessed, managed, and updated.

9
New cards

Database

allow multiple users and applications to work with data efficiently

10
New cards

Database

like a digital filing cabinet, where files are arranged systematically

11
New cards

Database system

an organized collection of data, along with the software (DBMS) that helps manage and retrieve this data efficiently

12
New cards

Database system

Database + Database Management System (DBMS)

13
New cards

Database system

a complete environment where data is stored, managed, and accessed

14
New cards

Database system

ensure accuracy, consistency, and efficiency.

15
New cards

DBMS

a software that helps users interact with the database.
Functions: Create, update, and delete data, Control access and security, Backup and recovery, Ensure data consistency and integrity

16
New cards

RDBMS(Relational Database Management System)

MySQL, Oracle Database, Microsoft SQL Server, PostgreSQL

17
New cards

NoSQL DBMS

MongoDB, Cassandra, CouchDB

18
New cards

Role of DBMS

Data Storage, Data Retrieval, Security, Backup & Recovery, Concurrency Control

19
New cards

Data Storage

organizes data into structured tables

20
New cards

Data Retrieval

provides SQL queries to search information

21
New cards

Security

manages access control (e.g., only admins can delete records)

22
New cards

Backup & Recovery

ensures data safety during failures

23
New cards

Concurrency Control

allows multiple users to access the same database simultaneously

24
New cards

Advantages of DBMS

Reduces redundancy, Improves consistency, Data security, Scalability, Better decision-making

25
New cards

Reduces redundancy

no repeated storage of same data

26
New cards

Improves consistency

single source of truth

27
New cards

Data security

user authentication and access control

28
New cards

Scalability

databases can grow as business grows

29
New cards

Better decision-making

through queries and reports

30
New cards

American National Standards Institute (ANSI)

has established a three-level architecture for a DBMS: internal, conceptual, and external

31
New cards

Internal level

determines where data is stored on the storage devices. This level deals with low-level access methods and how bytes are transferred to and from storage devices. In other words, this level interacts directly with the hardware.

32
New cards

Conceptual level

defines the logical view of the data. The data model is defined on this level, and the main functions of the DBMS, such as queries, are also on this level. The DBMS changes the internal view of data to the external view that users need to see. This level is an intermediary and frees users from dealing with the internal level.

33
New cards

External level

interacts directly with the user (end users or application programs). It changes the data coming from the conceptual level to a format and view that is familiar to the users.

34
New cards

Types of Databases

Hierarchical Database, Network Database, Relational Database(RDBMS), Object-Oriented Database, NoSQL Database

35
New cards

Hierarchical Database

stores data in a tree-like structure.( Old systems, e.g., IBM IMS)

36
New cards

Network Database

allows more complex relationships (many to many)

37
New cards

Relational Database (RDBMS)

stores data in tables (rows and columns). Most common today

38
New cards

Object-Oriented Database

stores data as objects (used in programming applications).

39
New cards

NoSQL Database

designed for unstructured or big data (e.g., MongoDB, Cassandra).

40
New cards

Structured Database

-database where data is organized in a predefined format (rows and columns)
-Uses Relational Database Management Systems (RDBMS) such as MySQL, Oracle, or PostgreSQL.
-Data fits neatly into tables with fixed fields and relationships.
Simple analogy: Like an Excel spreadsheet—everything has rows and columns with clear labels.

41
New cards

Unstructured Database

• A database that stores data without a predefined model or strict structure
. • Often managed using NoSQL databases (MongoDB, Cassandra, CouchDB).

• Handles data types such as text, images, videos, audio, logs, social media posts, emails.
Simple analogy: Like a folder full of mixed files (PDFs, images, videos) without a uniform format.

42
New cards

Database design

the process of organizing data into logical structures (tables, columns, relationships) before actual implementation

43
New cards

file-based system

early method of storing and managing data where each application has its own separate files to store information
• Data is kept in flat files (like text files or spreadsheets).
• Each application program is responsible for creating, managing, and accessing its own files.
• There is no central management of data

44
New cards

Data redundancy

same data repeated in many files.

45
New cards

Data inconsistency

If data is updated in one file but not in others → mismatch

46
New cards

Poor security

Each application controls its own file → hard to enforce consistent security.

47
New cards

Limited data sharing

Files are isolated → difficult to share across different departments.

48
New cards

Structural

refers to the organization or arrangement of data inside the database—meaning how the database is physically or logically structured.

49
New cards

Structural Dependence

• A condition where any change in the database structure (like adding a new column to a table) requires changes in all the application programs that access that data.
• Common in file-based systems.
• Example: If you add a new field “Email” to a Students file, all programs using that file must be modified.

50
New cards

Structural Independence

• A condition where you can change the database structure without affecting the application programs.
• Provided by DBMS.
• Example: Adding “Email” to a Students table in a relational database does not require changes in existing queries if they don’t use that field.

51
New cards

Data Dependence

A condition where the way data is stored directly affects how applications access it.
• If you change the structure of the data (like adding a field or changing data type), then all programs that use that data must also be modified.
• Common in file-based systems.

52
New cards

Data Independence

• A condition where applications are not affected by changes in the way data is stored or structured.
• Achieved using a DBMS because it provides a layer of abstraction between programs and physical storage.
• DBMS handles changes, so applications can continue working without modifications.

53
New cards

Data redundancy

occurs when the same piece of data is stored in multiple places (files or tables)

54
New cards

Storage Waste

Same data stored many times.

55
New cards

Update Problems

If Maria changes her address, you need to update all files

56
New cards

Inconsistency Risk

One file may have the new address, while another still has the old one

57
New cards

Data anomalies

are inconsistencies or errors that occur in a database due to poor design or redundancy. They usually occur in un-normalized databases (when tables are not organized properly).

58
New cards

Update Anomaly

When data is duplicated, updating one record but not the others lead to inconsistency.

59
New cards

Insert Anomaly

Cannot add new data because some other data is missing

60
New cards

Delete Anomaly

Removing a record deletes unintended information

61
New cards

one to one, one to many, many to many

Three types of data relationshhip

62
New cards

Physical, logical, view levels

Three degrees of data abstraction

63
New cards

data model

a conceptual framework that describes how data is represented, organized, and manipulated within a database system. Think of it as an architect's blueprint for a database.

64
New cards

data model

tells how the logical structure of a database is modeled

65
New cards

Data model

define how data is connected to each other and how it will be processed and stored inside the system

66
New cards

Provide Clarity

They offer a clear and unambiguous structure for how data is stored, related, and accessed

67
New cards

Improve Communication

They create a common language for both technical teams and business stakeholders, ensuring everyone is on the same page

68
New cards

Enhance Data Integrity

By defining rules and relationships, they help reduce redundancy and prevent inconsistencies in the data

69
New cards

Guide Implementation

They serve as a roadmap for building the actual database and a reference for future maintenance and updates

70
New cards

Entities, Attributes, Relationships

Key Building Blocks of a Data Model

71
New cards

Entity

any real-world object, person, place, or concept about which data is stored. For example, in a university database, Student, Course, and Professor are entities.

72
New cards

attribute

a property or characteristic of an entity. For Student, attributes might include StudentID, FirstName, and Major.

73
New cards

relationship

defines how two or more entities are associated with each other. For example, a Student enrolls in a Course.

74
New cards

Entity-Relationship Diagrams

(ER) Diagrams

75
New cards

Cardinality

in a database (or in an Entity-Relationship Diagram, ERD) describes the number of instances of one entity that can be associated with instances of another entity

76
New cards

junction table or associative entity

In a relational database, M:N relationships cannot be implemented directly. We must create a third table, called a

77
New cards

Hierarchical

1960s, Tree-like (one parent per child), Very fast for navigating defined paths., Rigid and inflexible; cannot model many-to many relationships easily.

78
New cards

Network

1970s, Graph-like (multiple parents per child), More flexible than hierarchical; directly models M:N relationships., Overly complex and difficult to query and maintain.

79
New cards

Relational

1970s Present, Tables (relations) with rows and columns, Simple, flexible, and powerful. Still the most, Can be less efficient for navigating deeply connected data.

80
New cards

Object Oriented

1980s 1990s, Objects with attributes and methods, Integrates well with object oriented programming; good for complex data types., Niche use cases; less support and standardization than relational models.

81
New cards

NoSQL

2000s Present, Varies (Document, Key-Value, Graph, etc.), Highly scalable and flexible; handles unstructured and "big data" perfectly., Weaker consistency guarantees (eventual consistency) compared to relational models.

82
New cards

hierarchical model

data is organized as an inverted tree. Each entity has only one parent but can have several children. At the top of the hierarchy, there is one entity, which is called the root.

83
New cards

network model

the entities are organized in a graph, in which some entities can be accessed through several paths

84
New cards

relational model

data is organized in two-dimensional tables called relations. The tables or relations are, however, related to each other, as we will see shortly.

85
New cards

RDBMS

the data is represented as a set of relations

86
New cards

relation

appears as a two-dimensional table

87
New cards

Name

Each relation in a relational database should have a name that is unique among other relations

88
New cards

Attributes

Each column in a relation is called an ___. These are the column headings in the table above

89
New cards

Tuples

Each row in a relation is called a __. It defines a collection of attribute values

90
New cards

Physical Level (Lowest) – INTERNAL VIEW

o This is the lowest level and describes how the data is actually stored on a physical device. It deals with files, memory blocks, indexes, and disk organization.
o This level is the most complex and is managed by the Database Management System (DBMS) and database administrators. It is hidden from most users.
o Example: A student record is stored in a specific data block on a hard drive, with an index on StudentID for fast lookups.

91
New cards

Logical Level (Middle) – EXTERNAL VIEW

o This level describes what data is stored and what relationships exist among that data. It defines all the tables, columns (with their data types), and relationships in the entire database.
o This is the level where database designers and developers work. It provides a complete view of the database structure without worrying about the physical implementation.
o Example: The database contains a Student table with columns like StudentID (Integer), Name (Text), and a Course table related through a foreign key.

92
New cards

View Level (Highest)

o This is the user's perspective. It shows only a small part of the database relevant to a specific user or application, hiding the rest. A single database can have many different views.
o This level provides security by restricting access and simplifies interaction for end-users.
o Example: A professor has a view that only shows the StudentID and Name of students enrolled in their specific courses, hiding student financial data and courses taught by other professors.

93
New cards

relational database model

94
New cards

E.F. Codd

who developed the relational database model

95
New cards

Predicate logic and Set Theory

The relational model, introduced by E. F. Codd in 1970, is based on ___ and ___

96
New cards

Predicate logic

used extensively in mathematics to provide a framework in which an assertion (statement of fact) can be verified as either true or false. Example: A student with a student ID of 324452 is named Mark Reyes.

97
New cards

Set theory

is a part of mathematical science that deals with sets, or groups of things, and is used as the basis for data manipulation in the relational model. Example: Set A contains 15, 23, and 52 while Set B contains 41, 52, 70, 12. It can be concluded that the A and B share a common value, 52.

98
New cards

name/table/entity

is as a two-dimensional structure composed of rows and columns.

99
New cards

Tuple

Each table row ___ represents data about an entity

100
New cards

attribute

Each table column represents an ___