1

DBMS
ARCHITECTURE
SCHEMA
LEVELS AND
MAPPING
WHAT IS DBMS?
DBMS contains information about a particular enterprise.

Computerized record keeping system

Provides convenient environment to user to perform

operations:
 Creation
Insertion

Deletion

Updating and retrieval of information

3
THREE LEVELS OF
ARCHITECTURE
 Also called ANSI/SPARC(American
National Standards institute/Standards
Planning And Requirements Committee) or
three schema architecture

 This framework is used for describing the

structure of specific database systems but
small systems may not support it as it
takes more time.

4
5
1.
EXTERNAL
LEVEL
6
 Highest or top level of data abstraction

 Related to the data which is viewed by individual

end users

 Includes a number of user views or external

schemas

 For example, an accounts department may only be

interested in the student fee details. It would not be
expected to have any interest in the personal
information about the students.

 Describes the segment of the database that is

required for a particular user group and hides the
rest of the database from that user group. 7
2.
CONCEPTUAL
LEVEL
 Also called as the data model

 Describes the structure of the whole database for a

group of users

 Representation of the entire content of the database

 Contains all the information to build relevant external

records

 Hides the internal details of physical storage

 Only one conceptual view for a single database

9
3.
PHYSICAL
LEVEL
 Also known as inner level

 Describes the physical storage structure of data in

database

 At lowest level, it is stored in the form of bits with the

physical addresses on the secondary storage device.

 At highest level, it can be viewed in the form of files.

 The internal schema defines the various stored data

types.

 Uses a physical data model

11
12
Want big impact?
Use big image.

13
OBJECTIVES OF
THREE LEVEL
SCHEMA
 Each user should be able to access the same data but
have a different customize view of the data.

 User should not have to deal directly with physical

database storage detail

 DBA should be able to change the conceptual

structure and be able to change the database storage
without affecting all users.

 The internal structure of the database should be

unaffected by changes to the physical aspects of
storage.

15
MAPPING AND
DATA
INDEPENDENCE
 The key for providing data independence.

 Data independence is the capacity to change the

schema at one level without having to change the
schema at the next higher level.

TYPES OF DATA INDEPENDENCE

1)Logical data independence

2)Physical data independence

17
1)LOGICAL DATA INDEPENDENCE:
 Provided by external/conceptual mapping

 Ability to modify conceptual schema without changing

external view and application programs

2) PHYSICAL DATA INDEPENDENCE:

 Provided by conceptual/internal schema

 Ability to modify internal or physical schema without

changing conceptual or view level schema and application
programs

18
THANK YOU