DBMS- History, Architecture

Prepared By
Dr.R.Kaladevi
ASP, Dept of CSE, Saveetha Engineering College
 History
• Charles Bachman developed the Integrated Data Store in early
1960’s based on network model
• In the late 1960’s, IBM developed Integrated Management
Systems based on hierarchical model.
• Edgar Codd developed Relational model in 1970’s
• IBM developed the Structured Query Language(SQL) in late
1980’s.
– It was declared as a standard language for the queries by ISO and
ANSI.
DBMS-History
Evolution of Databases
DBMS Three Level Architecture Diagram or Data abstraction
 Data Abstraction
• Physical level - The lowest level of abstraction describes how
the data are actually stored.
• Logical level. The next-higher level of abstraction describes
what data are stored in the database, and what relationships
exist among those data.
• The user of the logical level does not need to be aware of
physical level complexity is referred as physical data
independence.
 Data Abstraction Contd

• View level- The highest level of abstraction describes only

part of the entire database.
• Logical data independence: The ability to change the
Conceptual (Logical) schema without changing the External
schema (User View) is called logical data independence.
Two Tier and Three Tier Architecture
Database Architecture
 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
• Naïve users – invoke one of the permanent application
programs that have been written previously
– E.g. people accessing database over the web, bank tellers, clerical staf
 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
 Query Processor
• DDL interpreter-interprets DDL statements and records the
definitions in the data dictionary
• DML compiler which translates DML statements in a query
language into an evaluation plan
• Query optimization; that is, it picks the lowest cost evaluation
plan from among the alternatives.
• Query evaluation engine, which executes low-level
instructions generated by the DML compiler.
 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.
 Storage Management
• Storage manager is act as interface between the low-level
data and the application programs and queries
• Authorization and integrity manager-integrity constraints
and checks the authority of users
• Transaction manager, which ensures that the database
remains in a consistent (correct) state
• File manager, which manages the allocation of space on disk
storage and the data structures
• Buffer manager, which is responsible for fetching data from
disk storage into main memory, and deciding what data to
cache in main memory
 Disk Storage
• Data files, which store the database itself.
• Data dictionary, which stores metadata about
the structure of the database
• Indices, which can provide fast access to data
items
 Assignment
• Explain data abstraction with physical, logical
and view levels.
• Draw and explain DBMS architecture in detail
• Differentiate 2 tier and 3 tier architecture with
neat sketch