Database System Concepts and Architecture
Database System Concepts and Architecture
System
Instructor:
Tayyba Sana
Lecture Topic:
• Three-Schema Architecture
• Data Independence
• Logical Independence
• Physical Independence
• Summary
First Name: Rana Name: R. Aslam
Last Name: Aslam Saleema Age: 24y,10d
Date of Birth: Dept: Sales
12 Sep, 1970
Saleem
01110011010011100101001010100101010010101…..
Objectives of Three-Level Architecture
• All users should be able to access same data but have a different
customized view
• A user’s view is immune to changes made in other views
• Users should not need to know physical database storage details
Objectives of Three-Level Architecture..
• External Level
• Users’ view of the database
• Describes that part of database that is relevant to a
particular user
• Different views may have different representation
of same data (e.g. different date formats, age
derived from DOB etc.)
ANSI-SPARC Three-Level Architecture..
• Conceptual Level
• Community view of the database
• Describes what data is stored in database and
relationships among the data
• Along with any constraints on data
• Independent of any storage considerations
ANSI-SPARC Three-Level Architecture..
• Internal Level
• Physical representation of the database on the
computer
• Describes how the data is stored in the database
• physical implementation of the database to achieve
optimal runtime performance and storage space
utilization
• Data structures and file organizations used to store
data on storage devices
• Interfaces with the operating system access methods
to place the data on the storage devices, build the
indexes, retrieve the data, and so on
Differences between Three Levels of ANSI-SPARC
Architecture
Schemas
• External Schemas
• Also called subschemas
• Multiple schemas per database
• Corresponds to different views of data
• Conceptual Schema
• Describes all the entities, attributes, and
relationships together with integrity constraints
• Only one schema per database
Schemas..
• Internal Schema
• A complete description of the internal model,
containing the definitions of stored records, the
methods of representation, the data fields, and the
indexes and storage structures used
• Only one schema per database
Mappings
• Database Schema
• Description of database (also called intension)
• Specified during design phase
• Remain almost static
• Database Instance
• Data in the database at any particular point in
time
• Dynamic (changes with the time)
• Also called an extension (or state) of database
Data Independence