Scribd
Upload
68 views13 pages

Dbms Concepts & Architecture: Presented By:-Priyanka Naveen CDAC, Noida

The document discusses DBMS concepts and architecture. It describes the evolution from monolithic to modular client-server architectures. It also discusses data models including conceptual, physical and representational models. The three schema architecture of DBMS including internal, conceptual and external schemas is explained to achieve insulation of programs and data and support multiple user views. Data independence allows changes to the conceptual or internal schemas without affecting other schemas.

Uploaded by

[email protected]
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
68 views13 pages

Dbms Concepts & Architecture: Presented By:-Priyanka Naveen CDAC, Noida

The document discusses DBMS concepts and architecture. It describes the evolution from monolithic to modular client-server architectures. It also discusses data models including conceptual, physical and representational models. The three schema architecture of DBMS including internal, conceptual and external schemas is explained to achieve insulation of programs and data and support multiple user views. Data independence allows changes to the conceptual or internal schemas without affecting other schemas.

Uploaded by

[email protected]
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 13

DBMS CONCEPTS &

ARCHITECTURE

Presented By:-
Priyanka Naveen
CDAC, Noida
1. OVERVIEW

 The architecture of DBMS package has evolved from


the early monolithic systems (one tightly-integrated
system), to modern DBMS which are modular in
design, with a client-server architecture.
Client-Server Architecture

1. Connect

2. Request

3. Reply
4. Response

Client Module Server Module


2. DATA MODELS
 One fundamental characteristic of the database approach is to
provide some level of data abstraction by hiding details of data
storage not needed by most users
 Data Models; a collection of concepts that can be used to describe
the structure of a database
– Provides the necessary means to achieve the abstraction
– Structure of a database, includes data types, relationships
& Constraints
– includes a set of basic operations for specifying retrievals
& updates on the database
– Dynamic aspect / Behavior; specifying a set of user-defined
operations
DATA MODELS
: Categories
 High-level / Conceptual Data Model
– The way data is perceived by the end-user
 Low-level / Physical Data Model
– The way data is stored physically inside the computer
– Meant for computer-specialists

Between the two extremes is the “Representational /


Implementation data model” , providing concepts that
may be understood by the end-user but isn’t isolated from
the way data is stored in the computer.
CONCEPTUAL DATA MODEL

 Uses concepts, such as


– Entities; a real-world object or concept
– Attribute; some property related to an entity
– Relationship; interaction between two or more
entities
Some Essential Terminology
 In a data model, it is necessary to distinguish between the
description of the database and the database itself.
– Database Schema; the description of the database
– Schema Construct; an object defined in a schemas
– Database State/Snapshot; the data in database at a particular
state
– Database Metadata; the descriptions of the schema constructs
and constraints
– Intension (Database Schema) /Extension (Database State)
– Schema Evolution
3. DBMS ARCHITECTURE
 Three essential features of DBMS are
– Insulation of program & data
– Support for multiple user-views
– Use of a catalog to store the database description
(schema)

A three-schema architecture of DBMS help achieve


and visualize these features.
 The goal of three-schema architecture is to separate the user
applications and the physical database.
– The Internal Level (Internal Schema)
• Physical storage structure of the database
• Uses physical data model & describes details of data storage
& access paths
– The Conceptual Level (Conceptual Schema)
• Describes the structure of whole database
• Hides the details of physical storage structures
• Describes entities, data types, relationships, user-operations,
constraints
• Uses high-level / implementation data model
– The External/View Level (External Schema/User Views)
• Each external schema describes the part of the database
that a particular user group is interested in.
• Uses high-level / implementation data model.
THREE SCHEMA ARCHITECTURE
END USERS

EXTERNAL LEVEL EXTERNAL VIEW EXTERNAL VIEW

External/Conceptual Mapping

CONCEPTUAL LEVEL CONCEPTUAL SCHEMA

Conceptual /Internal Mapping

INTERNAL LEVEL INTERNAL SCHEMA

STORED DATABASE
THREE SCHEMA ARCHITECTURE
 A user-friendly tool to visualize the schema levels in the
database system.
 Mostly, DBs do not separate the three levels completely, but
support it to some limit.
 Three schemas are only descriptions of data; the actual data
exists at the physical level.
 Mappings; The process of transforming requests and results
between levels.
– May be time-consuming, hence some databases do not
support external view
4. DATA INDEPENDENCE
 Data Independence can be defined as the capacity to change
the schema at one level, without having to change the schema
at next higher level.
– Logical Data Independence; the capacity to change the
conceptual schema without having to change external
schema or application programs.
• The change in view definition, mappings, and/or
constraints
– Physical Data Independence; the capacity to change the
internal schema without having to change the conceptual /
external schema.
• May be required so as to reorganize physical files (e.g.
creating additional access paths)

You might also like