Chapter 2
Chapter 2
Chapter Two
2
Parts of the Architecture…
a) Internal Level
That is, it is concerned with the way the data is physically stored.
It is the way the DBMS and the Operating system perceive the data.
It is concerned with how fields are represented, what physical sequence the
stored records are in, …
It deals with assembly and similar language commands.
3
Parts of the Architecture…
b) Conceptual/Logical level
It is the community view of the database as seen by the DBA.
This is the next-higher level of abstraction next to internal level that
describes what data are stored in the database, and what relationships exist
among those data.
It includes Entity-Relationship modeling, security and integrity constraints.
Although implementation of the simple structure at the logical level may
involve complex physical-level structures, the user of the logical level does
not need to be aware of this complexity.
The logical level of abstraction is used by database administrators, who must
decide what information should be kept in the database.
4
Parts of the Architecture…
c) External/View level
The highest level of abstraction describes only some part of the entire
database.
It is concerned with how individual users view the database.
Despite the use of simpler structures at the logical level, some complexity
remains.
Because of the large size of the database, many users of the database system
will not be concerned with all this information.
Instead, such users need to access only a part of the database. So that their
interaction with the system is simplified and the view level of abstraction is
defined.
The system provides many views for the same database.
5
Parts of the Architecture…
For Example
6
Schemas and Instances
Schema
Isthe overall description of the database, include explanation of the database
constraints that should hold on the database.
The three level of schema according their abstraction: entity describes
External schema: at the external level to describe the various user
views.
Conceptual schema: at the conceptual level to describe the structure
and constraints for the whole database for a community of users. Uses
a conceptual or an implementation data model.
Internal schema: at the internal level to describe physical storage
structures and access paths.
7
Schemas and Instances…
Instances
is the collection of data in the database at a particular point of time.
Also called State or Snap Shot or Extension of the database
State of database is changed any time we add, delete or update an item.
Since Instance is actual data of database at some point in time, changes
rapidly.
Mappings
The DBMS is responsible for mapping between the 3 types of schema.
The conceptual schema is related to the internal schema through a
Conceptual/Internal mapping.
Each External schema is related to the conceptual schema by the
External/Conceptual mapping
8
Data Independence
The ability to modify a schema definition in one level without
affecting a schema definition in the next higher level is called data
independence.
There are two levels of data independence:
Physical data Independence:
is the ability to modify the physical schema without causing application
programs to be rewritten.
Modifications at the physical level are occasionally necessary to improve
performance.
Logical data independence:
is the ability to modify the logical schema without causing application
programs to be rewritten.
Modifications at the logical level are necessary whenever the logical
structure of the database is altered