ITINMT

SESSION 2
DATABASE MANAGEMENT SYSTEM

PREPARED BY: JAYRELLE B. SY, Ph.D

INTRODUCTION TO DBMS
DATABASE MANAGEMENT SYSTEM

▪ A database is an organized collection of data, generally stored

and accessed electronically from a computer system.

▪ Database System - Composed of 5 major parts: Hardware,

Software (DBMS), People, Procedures, and Data. (HSPPD)

▪ It is a suite of software
applications that together
make it possible for people
or business to
STORE, MODIFY
and EXTRACT information
from a database.
DATABASE MANAGEMENT SYSTEM

Figure 1: Simplified database

system environment
(ElMasri & Navathe, 2011)
CHARACTERISTICS OF DBMS
CHARACTERISTICS OF DBMS
▪ Real-world entity − A modern DBMS is more realistic and uses
real-world entities to design its architecture. It uses the
behavior and attributes too.

▪ Relation-based tables − DBMS allows entities and relations

among them to form tables. A user can understand the
architecture of a database just by looking at the table names.

▪ Less redundancy − DBMS follows the rules of normalization,

which splits a relation when any of its attributes is having
redundancy in values. Normalization is a mathematically rich
and scientific process that reduces data redundancy.
CHARACTERISTICS OF DBMS
▪ Consistency − Consistency is a state where every relation in a
database remains consistent . There exist methods and
techniques , which can detect attempt of leaving database in
inconsistent state.

▪ Query Language − DBMS is equipped with query language, which

makes it more efficient to retrieve and manipulate data. A user
can apply as many and as different filtering options as required to
retrieve a set of data
CHARACTERISTICS OF DBMS
▪ Multiuser and Concurrent Access − DBMS supports multi-
user environment and allows them to access and manipulate
data in parallel. Though there are restrictions on transactions
when users attempt to handle the same data item, but users
are always unaware of them.

▪ Multiple views − DBMS offers multiple views for different

users. A user who is in the Sales department will have a
different view of database than a person working in the
Production department. This feature enables the users to
have a concentrate view of the database according to their
requirements.
CHARACTERISTICS OF DBMS
▪ Security − Features like multiple views offer security to some
extent where users are unable to access data of other users
and departments. DBMS offers methods to impose constraints
while entering data into the database and retrieving the same
at a later stage. DBMS offers many different levels of security
features, which enables multiple users to have different views
with different features.
POPULAR DBMS
▪ Server DBMS
▪ Oracle
▪ SQL Server
▪ DB2
▪ MySQL, Firebird, PostgreSQL, (Significant open source DBMS)

▪ Desktop DBMS
▪ Microsoft Access
▪ FoxPro, Paradox, Approach, FileMaker Pro
USERS
USERS
USERS
▪ Administrators − Administrators maintain the DBMS and
are responsible for administrating the database.

▪ They are responsible to look after its usage and by whom it

should be used.

▪ They create access profiles for users and apply limitations to

maintain isolation and force security.

▪ Administrators also look after DBMS resources like system

license, required tools, and other software and hardware
related maintenance.
USERS
▪ Designers − Designers are the group of people who
actually work on the designing part of the database.

▪ They keep a close watch on what data should be kept and

in what format.

▪ They identify and design the whole set of entities,

relations, constraints, and views.
USERS
▪ End Users − End users are those who actually reap the
benefits of having a DBMS.

▪ End users can range from simple viewers who pay

attention to the logs or market rates to sophisticated
users such as business analysts.
DBMS & SCHEMA ARCHITECTURE
DBMS ARCHITECTURE
▪ The design of a DBMS depends on its architecture. It
can be centralized or decentralized or hierarchical.

▪ DBMS architecture depends upon how users are

connected to the database to get their request done.

▪ The architecture of DBMS depends on the computer

system on which it runs.
DBMS ARCHITECTURE
1 TIER ARCHITECTURE
▪ It is where the Client, Server, and Database all reside
on the SAME MACHINE.

▪ In this architecture, the database is directly available to

the user. It means the user can directly sit on the DBMS
and uses it.

▪ The 1-Tier architecture is used for development of

the local application, where programmers can directly
communicate with the database for the quick response.

▪ But such architecture is rarely used in production.

1 TIER ARCHITECTURE
▪ Anytime you install a DB in your system and access it
to practice SQL queries it is 1 tier architecture.
2 TIER ARCHITECTURE
▪ The database system is present at the server machine and
the DBMS application is present at the client machine,
these two machines are connected with each other through a
reliable network.

▪ Whenever client machine makes a request to access the

database present at server using a query language, the server
perform the request on the database and returns the result
back to the client.

▪ The application connection interface such as JDBC, ODBC are

used for the interaction between server and client.
2 TIER ARCHITECTURE
3 TIER ARCHITECTURE
▪ A 3-tier architecture separates
its tiers from each other based
on the complexity of the users
and how they use the data
present in the database.

▪ It is the most widely used

architecture to design a DBMS.
3 TIER ARCHITECTURE
▪ This DBMS architecture contains an Application layer
between the user and the DBMS, which is responsible for
communicating the user's request to the DBMS system and
send the response from the DBMS to the user.
3 LEVEL SCHEMA ARCHITECTURE
▪ The term "schema" refers to the organization of data as a
blueprint of how the database is constructed.

▪ Database systems comprise of complex data structures. Thus,

to make the system efficient for retrieval of data and reduce
the complexity of the users, developers use the method of Data
Abstraction.
THREE SCHEMA ARCHITECTURE
EXTERNAL(VIEW) LEVEL
▪ Several users can view their desired data from this level which
is internally fetched from database with the help of conceptual
and internal level mapping.

▪ The user doesn’t need to know the database schema details

such as data structure, table definition etc. user is only
concerned about data which is what returned back to the view
level after it has been fetched from database

▪ EXTERNAL LEVEL is the “TOP LEVEL” of the Three Level of

Schema Architecture.
CONCEPTUAL(LOGICAL) LEVEL
▪ It is also called logical level. The whole design of the
database such as relationship among data, schema of
data etc. are described in this level.

▪ Database constraints and security are also implemented in

this level of architecture. This level is maintained by DBA
(database administrator).
INTERNAL(PHYSICAL) LEVEL
▪ This level is also known as physical level. This level
describes how the data is actually stored in the
storage devices. This level is also responsible for
allocating space to the data. This is the lowest level of
the architecture.
EXAMPLE
▪ Let’s say we are storing customer information in a customer
table.

▪ At physical level these records can be described as blocks of

storage (bytes, gigabytes, terabytes etc.) in memory. These
details are often hidden from the programmers.

▪ At the logical level these records can be described as fields

and attributes along with their data types, their relationship
among each other can be logically implemented.
▪ The programmers generally work at this level because they are
aware of such things about database systems.
EXAMPLE
▪ At view level, user just interact with system with the
help of GUI and enter the details at the screen, they are
not aware of how the data is stored and what data is
stored; such details are hidden from them.
SCHEMA VS INSTANCE
▪ Database schema is the SKELETON OF DATABASE . It is
designed when the database doesn 't exist at all. Once the
database is operational , it is very difficult to make any
changes to it. A database schema does not contain any data
or information.

▪ The data stored in database at a particular moment of time

is called instance of database. Database schema defines the
variable declarations in tables that belong to a particular
database; the value of these variables at a moment of time is
called the instance of that database.
SCHEMA VS INSTANCE
▪ For example, lets say we have a single table student in
the database, today the table has 100 records, so today
the instance of the database has 100 records.

▪ Lets say we are going to add another 100 records in this

table by tomorrow so the instance of database tomorrow
will have 200 records in table.

▪ In short, at a particular moment the data stored in

database is called the instance, that changes over time
when we add or delete data from the database.
DATA INDEPENDENCE
 DATA INDEPENDENCE
▪ Data independence refers
characteristic of being able
to modify the schema at
one level of the database
system without altering the
schema at the next higher
level.
▪ Types of Data Independence
▪ Logical Data Independence
▪ Physical Data Independence
DATA INDEPENDENCE
Logical Data Independence
▪ Refers characteristic of being able to change the
conceptual schema without having to change the
external schema.

▪ Logical data independence is used to separate the

external level from the conceptual view.

▪ If we do any changes in the conceptual view of the data,

then the user view of the data would not be affected.
DATA INDEPENDENCE
▪ Example:
▪ The name field in the conceptual view is stored as first
name, middle name and last name whereas in external
view, it remains to be a single name field.
DATA INDEPENDENCE
Physical data independence
▪ The capacity to change the internal schema without
having to change the conceptual schema.

▪ If we do any changes in the storage size of the database

system server, then the Conceptual structure of the
database will not be affected.

▪ Physical data independence is used to separate

conceptual levels from the internal levels.
DATA INDEPENDENCE
▪ The location of the database, if changed from C
drive to D drive will not affect the conceptual
view or external view as the commands are
independent of the location of the database