Pimpri Chinchwad Education Trust’s

Pimpri Chinchwad College of Engineering and

Research, Pune

Presenter :
Mrs. Sonali Lunawat
Assistant Professor , Dept. of Computer
Engineering
1
 Introduction
to
Database
Management Systems
DATA, INFORMATION AND KNOWLEGDE

Simple

KNOWLED
PowerPoint
Presentation

GE
Simple
PowerPoint information that has been retained
Presentation
INFORMATI with an understanding
ON
Facts are learned .Roll No 1, Red
Color
DATA
RAW FACTS Like 1 ,RED, 50
 What Is a DBMS?
❖A very large, integrated collection of
data.
❖ Models real-world enterprise.
– Entities (e.g., students, courses)
– Relationships (e.g., Arjun is taking
CS564)
❖ A Database Management System
(DBMS) is a software package
designed to store and manage
4 databases.
 Why to Use a
DBMS
Data redundancy and inconsistency – Redundancy is the concept of
repetition of data i.e. each data may have more than a single copy. The file
system cannot control redundancy of data as each user defines and maintains
the needed files for a specific application to run. There may be a possibility that
two users are maintaining same files data for different applications.

Data sharing – File system does not allow sharing of data or sharing is too
complex. Whereas in DBMS, data can be shared easily due to centralized
system.

Data concurrency – Concurrent access to data means more than one user is
accessing the same data at the same time. Anomalies occur when changes
made by one user gets lost because of changes made by other user.

Data searching – For every search operation performed on file system, a

different application program has to be written

Data integrity – There may be cases when some constraints need to be

applied on the data before inserting it in database.
5 Database Management Systems, R. Ramakrishnan
 ?
Why Study Databases??

❖Shiftfrom computation to
information
❖Datasets increasing in diversity
and volume.

6
 Data Models

❖A data model is a collection of

concepts for describing data.

Many different model are present we

will learn in upcoming video

❖A schema is a description of a
particular collection of data, using
the a given data model.

7
 Levels of
Abstraction
❖ Many views, single View View View
conceptual (logical) 1 2 3
schema and
Conceptual
physical schema.
Schema
– Views describe how
Physical
users see the data.
Schema
– Conceptual schema
defines logical
structure
– Physical schema
describes the files
and indexes used.

8
 Data Independence
❖ Applications insulated from how data is
structured and stored.
❖ Logical data independence: Protection from
changes in logical structure of data.
❖ Physical data independence: Protection from
changes in physical structure of data.

☛ One of the most important benefits of using a DBMS!

9
 ❖ Database administrator (DBA)
– Designs logical / physical schemas
– Handles security and authorization
– Data availability, crash recovery
– Database tuning as needs evolve
Must understand how a DBMS works!

10
WHAT IS DATABASE DESIGN?
Database Design is a collection of
processes that facilitate the designing,
development, implementation and
maintenance of enterprise data
management systems.

It helps produce database systems

1. That meet the requirements of the
users
2. Have high performance.
Database development life cycle
 Database Architecture

The architecture of a database systems is the

underlying computer system on which the
database is running:

 Centralized
 Client-server
 Parallel (multi-processor)
 Distributed
Centralized Database Architecture
Client-Server Database Architecture
Parallel Database Architecture
Distributed Database
Architecture
 Data Models

❖A data model is a collection of

concepts for describing data.
❖ A schema is a description of a
particular collection of data, using
the a given data model.
❖ The relational model of data is the
most widely used model today.
 Main concept: relation, basically a table with
rows and columns.
 Every relation has a schema, which describes the
columns, or fields.
18
Let’s Think

 If you want a build a house what you

will prefer to start with the process of
building house
 Data Models

 A collection of tools for describing

 Data
 Data relationships
 Data semantics
 Data constraints
 Types of Data Models
 Network Model
 Hierarchical Model
 Entity-relationship Model
 Relational Model
 Object Relation Model
 XML
Hierarchical Model

Builder

Site
Manager

Worker 1 Worker 2 Worker 3

Network Model

Builder

Site
Owner
Manager
Relational Model
Entity-relationship Model
 Object-Relational Data Models
 Relational model: flat, “atomic” values
 Object Relational Data Models
 Extend the relational data model by including
object orientation and constructs to deal with
added data types.
 Allow attributes of tuples to have complex
types, including non-atomic values such as
nested relations.
 Preserve relational foundations, in particular the
declarative access to data, while extending
modeling power.
 Provide upward compatibility with existing
relational languages.
XML: Extensible Markup Language

 Defined by the WWW Consortium (W3C)

 Originally intended as a document markup
language not a database language
 The ability to specify new tags, and to create
nested tag structures made XML a great way to
exchange data, not just documents
 XML has become the basis for all new generation
data interchange formats.
 A wide variety of tools is available for parsing,
browsing and querying XML documents/data
Database System Internals
Database Users and Administrators
• Application Programmers are computer
professionals interacting with the system
through DML calls embedded in a program
written in a host language (e.g. C, PL/1, Pascal).

• Sophisticated Users interact with the system

without writing programs :They form requests by
writing queries in a database query language.
These are submitted to a query processor that
breaks a DML statement down into instructions
for the database

• Database Users : Administrate overall

process.

• Naive Users are unsophisticated users who

Database Engine

 Storage manager
 Query processing
 Transaction manager
 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 OS file manager
 Efficient storing, retrieving and updating of data
 Issues:
 Storage access
 File organization
 Indexing and hashing
 Query Processing
1. Parsing and translation
2. Optimization
3. Evaluation
Transaction Management
 What if the system fails?
 What if more than one user is concurrently
updating the same data?
 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.
Query processor
DML compiler
Translates the Data Manipulation Languages
into query Engine instructions. It might also do
optimization for query.

DML Linker
Converts the DML statements in the an
application program to normal procedure calls
in the host language.

DDL interpreter
Interprets DDL statements and records them in
a set of tables containing metadata

Query Evaluation Engine

Storage Manager
Authorization and integrity manager
Tests for the satisfaction of integrity constraints and Checks
the authority of user to perform various action.

Transaction Manager
Ensures the database remains in a consistent (correct) state
despite system failures.

File manager
Responsible for the allocation of space on the disk storage
system.

Buffer manager
Manages the data coming into and out of the system,
Including the caching of data.