Chapter No.02

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 25

Database Systems

Lecture: 03

Database Environment

Three Level Architecture


1
Recap of Basic Definitions

Database: A collection of related data that is organized


for quick retrieval of information.
DBMS: A software package / system to facilitate the
creation and maintenance of a computerized
database.
Database System: The DBMS software together with
data and application included as well.

2
Recap of Basic Definitions
Schema: The description of database is called database
Schema, which is specified during database design.
Single User System: In single user system at most one
user can access the database at any given time
Multi User System: Many user can access the database
at the same time
View: Allows each user to have his or her own view of
the database.

3
Chapter 2 - Objectives

Purpose of three-level database architecture.


Contents of external, conceptual, and internal levels.
Purpose of external/conceptual and conceptual/internal
mappings.
Meaning of logical and physical data independence.
Distinction between DDL and DML.
A classification of data models.

Three Level Architecture 4


Chapter 2 - Objectives
Purpose/importance of conceptual modelling.
Typical functions and services a DBMS should
provide.

Three Level Architecture


5
Related concepts
Data Abstraction
 Suppression of details of data
organization and storage
 System hides certain implementation
details of how data is stored,
created and maintained
 Complexity should be hidden from
database user
 Levels of Abstraction
 Physical Level
 Conceptual Level
 View Level
6
Database Architecture
In 1971, DBTG proposed a proposal
for a standard architecture for
database systems
In 1975, ANSI/SPARC also developed
similar architecture
As result of these efforts, Three
Level Architecture came into
existence

7
Objectives of Three-Level Architecture

All users should be able to access same data.

A user’s view is immune to changes made in


other views.

Users should not need to know physical


database storage details.

Three Level Architecture 8


Objectives of Three-Level Architecture
DBA should be able to change database storage
structures without affecting the users’ views.

Internal structure of database should be


unaffected by changes to physical aspects of
storage.

DBA should be able to change conceptual


structure of database without affecting all
users.

Three Level Architecture 9


ANSI-SPARC Three-Level Architecture

Three Level Architecture 10


ANSI-SPARC Three-Level Architecture

External Level
Users’ view of the database.
Conceptual Level
Community view of the database.
Internal Level
Physical representation of the database on the
computer.

Three Level Architecture 11


Differences between Three Levels
of ANSI-SPARC Architecture

Three Level Architecture 12


First Name: Hina Name: H.Ali
Last Name: Ali ABC Age: 24y,10d
Date of Birth: Dept: Sales
12 Sep, 1970
XYZ

Name DoB DepId

Hina Ali 12/09/70 D001


Maria Wasti 29/02/80 D005

BH RH Hina Ali120970 5 D001 RH Maria Wasti…

01110011010011100101001010100101010010101…..
Data Independence

Logical Data Independence


Refers to immunity of external schemas to
changes in conceptual schema.
Physical Data Independence
Refers to immunity of conceptual schema to
changes in the internal schema.

Three Level Architecture 14


Data Independence and the ANSI-
SPARC Three-Level Architecture

Three Level Architecture 15


Database Languages
Data Definition Language (DDL)
Allows the DBA or user to describe and name
entities, attributes, and relationships required
for the application
plus any associated integrity and security
constraints.

Three Level Architecture 16


Database Languages
Data Manipulation Language (DML)
Provides basic data manipulation operations on
data held in the database.
Procedural DML
allows user to tell system exactly how to
manipulate data.
Non-Procedural DML
allows user to state what data is needed rather
than how it is to be retrieved.
Fourth Generation Languages (4GLs)

Three Level Architecture 17


Data Model
Integrated collection of concepts for
describing data, relationships between data,
and constraints on the data in an
organization.
Data Model comprises:
a structural part; consisting of a set of rules
according to which databases can constructed
a manipulative part; defining the types of
operation that are allowed on data
possibly a set of integrity rules, which ensures
that data is accurate
Three Level Architecture 18
Data Model
Purpose
To represent data in an understandable way.

Categories of data models include:


Object-based
Record-based
Physical.

Three Level Architecture 19


Relational Data Model

Three Level Architecture 20


Conceptual Modeling

Conceptual modeling is process of developing a


model of information use that is independent
of implementation details.
Conceptual models are also referred to as
“logical Model”

Three Level Architecture 21


Functions of a DBMS
Data Storage, Retrieval, and Update.

A User-Accessible Catalog.

Transaction Support.

Concurrency Control Services.

Recovery Services.

Three Level Architecture 22


Functions of a DBMS
Authorization Services.

Support for Data Communication.

Integrity Services.

Services to Promote Data Independence.

Utility Services.

Three Level Architecture 23


System Catalog
Repository of information (metadata)
describing the data in the database.
One of the fundamental components of DBMS.
Typically stores:
names, types, and sizes of data items;
constraints on the data;
names of authorized users;
data items accessible by a user and the type of access;
usage statistics.

Three Level Architecture 24


Reference

Chapter No.2

Three Level Architecture 25

You might also like