DATA BASE MANAGEMENT SYSTEM

DBMS

05/25/24 1
 INTRODUCTION
• Purpose of Database Systems
• View of Data
• Data Models
• Data Definition Language
• Data Manipulation Language
• Transaction Management
• Storage Management
• Database Administrator
• Database Users
05/25/24 2
 DATABASE
• A database is a structured way of organizing and storing
information to be easily accessed, managed, and used to
support various tasks and operations.
• A database is like a digital filing cabinet where we can store
and organize information. It's a collection of data that is
organized in a way that makes it easy to search, access, and
manage.
• For example, think of a contact list on your phone. Each entry
in the contact list represents a piece of information about a
person, such as their name, phone number, and email address.
All these entries together make up the database of contacts on
your phone.
05/25/24 3
DATABASE MANAGEMENT SYSTEM
(DBMS)
• Collection of interrelated data
• Set of programs to access the data
• DBMS contains information about a particular enterprise
• DBMS provides an environment that is both convenient and
efficient to use.
• Database Applications:
• Banking: all transactions
• Airlines: reservations, schedules
• Universities: registration, grades
• Sales: customers, products, purchases
• Manufacturing: production, inventory, orders, supply chain
• Human resources: employee records, salaries, tax deductions
• Databases touch all aspects of our lives
05/25/24 4
PURPOSE OF DATABASE SYSTEM
• In the early days, database applications were built on top of file
systems
• Drawbacks of using file systems to store data:
• Data redundancy and inconsistency
• Multiple file formats, duplication of information in different files
• Difficulty in accessing data
• Need to write a new program to carry out each new task
• Data inaccessibility — multiple files and formats
• Integrity problems
• Integrity constraints (e.g. account balance > 0) become part of program
code
• Hard to add new constraints or change existing ones
05/25/24 5
 DATA ABSTRACTION

Data Abstraction is a process of hiding unwanted or

irrelevant details from the end user. It provides a different
view and helps in achieving data independence which is
used to enhance the security of data

05/25/24 6
 LEVELS OF ABSTRACTION

• Physical level describes how a record (e.g., customer) is stored.

• Logical level: describes data stored in database, and the
relationships among the data.
type customer = record
name : string;
street : string;
city : integer;
end;
• View level: application programs hide details of data types. Views
can also hide information (e.g., salary) for security purposes.
05/25/24 7
VIEW OF DATA

05/25/24 8
 INSTANCES AND SCHEMAS

The data which is stored in the database at a particular moment

of time is called an instance of the database. The overall design
of a database is called schema.

05/25/24 9
 INSTANCES
• An instance refers to a single occurrence or realization of a data
entity.
• In database terminology, an instance typically represents a specific
set of data values stored in a database at a given point in time.
• For example, if you have a database table for "employees," each
row in the table represents an instance of an employee, with
specific values for attributes such as name, ID, salary, etc.
• Instances are dynamic and can change over time as data is added,
modified, or deleted.

05/25/24 10
 SCHEMAS
• A schema is a formal description or blueprint that defines a database's
structure, organization, and constraints.
• It specifies the data types that can be stored in the database, the
relationships between different data entities, and the rules for accessing
and manipulating the data.
• A schema provides a framework for organizing and understanding the data
stored in a database, ensuring consistency and integrity of the data.
• It includes definitions of tables, attributes, data types, keys, constraints,
and other database objects.
• Schemas are static and do not change frequently once they are defined.
They serve as a reference for designing and managing the database.

05/25/24 11
 INSTANCES AND SCHEMAS
• Schema – the logical structure of the database
• e.g., the database consists of information about a set of customers and accounts and the
relationship between them)
• Analogous to type information of a variable in a program
• Physical schema: database design at the physical level
• Logical schema: database design at the logical level

• Physical Data Independence – the ability to modify the physical schema without
changing the logical schema
• Applications depend on the logical schema
• In general, the interfaces between the various levels and components should be well
defined so that changes in some parts do not seriously influence others.

05/25/24 12
 DATA MODELS

• A collection of tools for describing

• data
• data relationships
• data semantics
• data constraints

• Entity-Relationship model
• Relational model
• Other models:
• object-oriented model
• semi-structured data models
• Older models: network model and hierarchical model

05/25/24 13
 ENTITY-RELATIONSHIP MODEL

Example of schema in the entity-relationship model

05/25/24 14
ENTITY RELATIONSHIP MODEL
(CONT.)
• E-R model of real world
• Entities (objects)
• E.g. customers, accounts, bank branch
• Relationships between entities
• E.g. Account A-101 is held by customer Johnson
• Relationship set depositor associates customers with accounts

• Widely used for database design

• Database design in E-R model usually converted to design in the
relational model (coming up next) which is used for storage and
processing
05/25/24 15
A SAMPLE RELATIONAL
DATABASE

05/25/24 16
 DATA DEFINITION LANGUAGE
(DDL)
• Specification notation for defining the database schema
• E.g.
create table account (
account-number char(10),
balance integer)

• DDL compiler generates a set of tables stored in a data dictionary

• Data dictionary contains metadata (i.e., data about data)
• database schema
• Data storage and definition language
• language in which the storage structure and access methods used by the
database system are specified
• Usually an extension of the data definition language

05/25/24 17
 DATA MANIPULATION LANGUAGE
(DML)

• Language for accessing and manipulating the data organized

by the appropriate data model
• DML also known as query language
• Two classes of languages
• Procedural – user specifies what data is required and how to get
those data
• Nonprocedural – user specifies what data is required without
specifying how to get those data
• SQL is the most widely used query language
05/25/24 18
 SQL
• SQL: widely used non-procedural language
• E.g. find the name of the customer with customer-id 192-83-7465
select customer.customer-name
from customer
where customer.customer-id = ‘192-83-7465’
• E.g. find the balances of all accounts held by the customer with customer-id 192-83-
7465
select account.balance
from depositor, account
where depositor.customer-id = ‘192-83-7465’ and
depositor.account-number = account.account-number

• Application programs generally access databases through one of

• Language extensions to allow embedded SQL
• Application program interface (e.g. ODBC/JDBC) which allow SQL queries to be
05/25/24 19
sent to a database
 DATABASE USERS

• Users are differentiated by the way they expect to interact with the
system
• Application programmers – interact with system through DML calls
• Sophisticated users – form requests in a database query language
• Specialized users – write specialized database applications that do
not fit into the traditional data processing framework
• Naive users – invoke one of the permanent application programs
that have been written previously
• E.g. people accessing database over the web, bank tellers, clerical staff

05/25/24 20
 STORAGE MANAGEMENT

• Storage manager is a program module that provides the

interface between the low-level data stored in the database
and the application programs and queries submitted to the
system.
• The storage manager is responsible to the following tasks:
• interaction with the file manager
• efficient storing, retrieving and updating of data

05/25/24 21
 TRANSACTION MANAGEMENT

• A transaction is a collection of operations that performs a

single logical function in a database application
• Transaction-management component ensures that the database
remains in a consistent (correct) state despite system failures
(e.g., power failures and operating system crashes) and
transaction failures.
• Concurrency-control manager controls the interaction among
the concurrent transactions, to ensure the consistency of the
database.

05/25/24 22
 DATABASE ADMINISTRATOR
• Coordinates all the activities of the database system; the
database administrator has a good understanding of the
enterprise’s information resources and needs.
• Database administrator's duties include:
• Schema definition
• Storage structure and access method definition
• Schema and physical organization modification
• Granting user authority to access the database
• Specifying integrity constraints
• Acting as liaison with users
• Monitoring performance and responding to changes in requirements

05/25/24 23