1

CHAPTER 1:
FUNDAMENTALS OF
DATABASE
MANAGEMENT
SYSTEM

2
Course Learning Outcome

CLO1: Apply the fundamentals concepts

and structure of database management
and relational data model in database
development concepts.
(C3, PLO1)

3
Learning Outcome
 Understand database
 Understand DBMS
 Understand data model

4
Terminologies of database
• Data
• Known facts that can be recorded and have implicit
meaning
• Database
• A collection of related data.
• Database System
• Composed of 5 major parts: Hardware, Software (DBMS),
People, Procedures and Data
• Database Management System (DBMS)
• Collection of components that support data acquisition,
dissemination, storage, maintenance, retrieval, and
formatting

5
Evolution of database

6
 Flat files
• punched cards technology was used to store data – later, files.
But the files have no as such advantage, rather have several
limitations

Advantages Limitations
Various access methods , e.g., sequential, Requires extensive programming in third-generation language such as
indexed, random COBOL, BASIC.

Separation and isolation: Each program maintains its own set of data,
users of one program may not be aware of holding or blocking by other
programs that are being used somewhere else, by another user.

Duplication of data – same data is held by different programs, thus,

wastes space and resources.

High maintenance costs such as ensuing data consistency and controlling

access
Sharing granularity is very coarse.
Weak security.

7
Disadvantage of traditional approach

Data Mapping and Access

Data Redundancy

Data Dependence

Data inconsistency

Data Isolation

Security

Integrity

Atomicity

Concurrent Access

8
Hierarchical Data Model

Advantages Limitations

Efficient searching. Complex implementation

Less redundant data. Difficult to manage and lack of standards, can’t easily
handle many-many relationships.
Data independence. Lacks structural independence.

Database security and integrity.

9
Database Management System (DBMS)

• A set of software programs that allows users to create, edit

and update data in database files, and store and retrieve data
from those database files.
• Data in a database can be added, deleted, changed, sorted or
searched all using a DBMS.
• Example usage of Database System:
• Library information
• Accounting and bookkeeping information
• Customer information and Inventory information
• Personal records

10
 NoSQL
• information which they are unable to mine using RDBMS, they started
exploring ways to store such datasets.
• Anything which is not RDBMS today is loosely known as NoSQL.
• very difficult to store the data on RDBMS

11
Properties of databases
1. Completeness
2. Integrity
3. Flexibility
4. Efficiency
5. Usability

12
Completeness
• Ensures that users can access the data they want includes ad hoc
queries, which would not be explicitly given as part of a statement of
data requirements.
• Database has to support the requirements
• It requires the complete understanding of database structure,
relationship and constraint.

13
Integrity
• Ensures that data is both consistent (no contradictory data) and
correct (no invalid data), and ensures that users trust the database.
• Database integrity ensures that data entered into the database is
accurate, valid, and consistent.
• Any applicable integrity constraint and data validation rules must be
satisfied before permitting a change to the database.

14
Flexibility
• Ensures that a database can evolve (without requiring excessive
effort) to satisfy changing user requirements.
• Ability to upgrade or change the functionality of database up to
the current need.
• Ability to support wide area of data types

15
Efficiency
• Ensures that users do not have unduly long response times when
accessing data.
• The database should be able to perform effectively.
• The designer has to choose the right DBMS, the right access path in
order to improve the efficiency.

16
Usability
• Ensures that data can be accessed and manipulated in ways which
match user requirements.
• The database design significantly impacts the quality and usability of
the data.
• A database design that is not properly normalized will introduce data
update anomalies and data errors.
• A poorly designed database may place the entire organization at risk
due to the incomplete or incorrect information.

17
Database System Environment

Figure 1: Simplified database system environment (ElMasri & Navathe, 2011)

A Various Common of DBMS

• Server DBMS
• Oracle
• SQL Server
• DB2
• Significant open source DBMSs
• MySQL
• Firebird
• PostgreSQL

• Desktop DBMS
• Microsoft Access
• FoxPro, Paradox, Approach, FileMaker Pro

19
Common Features of DBMS
Features Description
Database Language and graphical tools to define entities,
definition relationships, integrity constraints, and authorization
rights.
Nonprocedural Language and graphical tools to access data without
access complicated coding
Application Graphical tools to develop menus, data entry forms, and
development reports; data requirements for forms and reports are
specified using nonprocedural access
Procedural Language that combines nonprocedural access with full
language interface capabilities of a programming language

Transactional Control mechanisms to prevent interference from

processing simultaneous users and recover lost data after a failure

Database tuning Tools to monitor and improve database performance 20

Advantage of DBMS

Data
Data Mapping Data
Independence
and Access Redundancy
and Consistency

Security Integrity Atomicity

Concurrent
Access

21
 complexity

large amount
of memory

DISADVANTAGES
OF DBMS

centralized
system

generalized
software

22
 TYPES OF DATABASES
Centralized Database
• all data is stored at a single site.
• It offers a great control in accessing
and updating data.
• failure chances are high because
the system depends on the
availability of resources at the
central site
Distributed Database
• the database is stored on several
computers.
• may communicate with one another
through internet/intranet/telephone
lines etc
• be geographically separated and
managed.
• separately be administered 23
24