Scribd
Upload
13 views17 pages

Chapter 2

The document discusses database system concepts and architecture, focusing on data models, schemas, and the three-schema architecture. It outlines the categories of data models, including conceptual, physical, and implementation models, and explains the distinction between database schema and state. Additionally, it covers data independence, emphasizing the ability to change schemas at different levels without affecting others.

Uploaded by

harsha.gowda1165
Copyright
© © All Rights Reserved
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
13 views17 pages

Chapter 2

The document discusses database system concepts and architecture, focusing on data models, schemas, and the three-schema architecture. It outlines the categories of data models, including conceptual, physical, and implementation models, and explains the distinction between database schema and state. Additionally, it covers data independence, emphasizing the ability to change schemas at different levels without affecting others.

Uploaded by

harsha.gowda1165
Copyright
© © All Rights Reserved
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/ 17

Copyright © 2007 Ramez Elmasri and Shamkant B.

Navathe Slide 2- 1
Chapter 2
Database System Concepts and
Architecture

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe


Outline
 Data Models and Their Categories
 History of Data Models
 Schemas, Instances, and States
 Three-Schema Architecture
 Data Independence
 DBMS Languages and Interfaces
 Database System Utilities and Tools
 Centralized and Client-Server Architectures
 Classification of DBMSs

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 3


Data Models
 Data Model:
 Its a collection of concepts that can be used to

describe the structure of a database


 provides the necessary means to achieve this

abstraction

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 4


Categories of Data Models
 Conceptual (high-level, semantic) data models:
 Provide concepts that are close to the way many users
perceive data.
 Physical (low-level, internal) data models:
 Provide concepts that describe details of how data is stored
in the computer.
 Implementation (representational) data models:
 Provide concepts that fall between the above two, used by
many commercial DBMS implementations (e.g. relational
data models used in many commercial systems).

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 5


Other Data models
 Entity–relationship model
 a popular high-level conceptual data model which
contains entities, attributes and relations
 Record-based data models.
 represent data by using record structures
 object data model
 higher-level implementation data models
 self-describing data models.
 The data storage in systems based on these
models combines the description of the data with
the data values themselves Slide 2- 6
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe
Schemas versus Instances
 Database Schema:
 The description of a database.
 Includes descriptions of the database structure,
data types and the constraints on the database.
 It doesn’t change frequently
 Schema Diagram:
 An illustrative display of a database schema.
 Schema changes are usually needed as the
requirements of the database applications change
 Schema Construct:
 A component of the schema or an object within
the schema, e.g., STUDENT, COURSE.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 7
Example of a Database Schema

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 8


Schemas versus Instances
 Database State:
 The data in database may change frequently
 The actual data stored in a database at a
particular moment in time is called database
state or snapshot.
 Also called database instance (or occurrence or
snapshot).

The term instance is also applied to individual
database components, e.g. record instance, table
instance, entity instance

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 9


Example of a database state

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 10


Database Schema
vs. Database State
 Database State:
 Refers to the content of a database at a moment
in time.
 Initial Database State:
 Refers to the database state when it is initially
loaded into the system.
 Valid State:
 A state that satisfies the structure and constraints
of the database.

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 11


Database Schema
vs. Database State (continued)
 Distinction
 The database schema changes very infrequently.
 The database state changes every time the
database is updated.

 Schema is also called intension.


 Database State is also called extension.

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 12


Three-Schema Architecture
 Proposed to support the following three DBMS
characteristics :
 Self describing nature
 Insulation of programs and data.
 Support of multiple views of the data.

 Main Goal: Separate the user application from


physical database.

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 13


Three-Schema Architecture
 Defines DBMS schemas at three levels:
 Internal schema at the internal level to describe physical
storage structures and access paths (e.g indexes).

Typically uses a physical data model.
 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.
 External schemas at the external level to describe the
various user views.

Usually uses the same data model as the conceptual schema.

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 14


The three-schema architecture

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 15


Three-Schema Architecture
 Mappings among schema levels are needed to
transform requests and data.
 Programs refer to an external schema, and are
mapped by the DBMS to the internal schema for
execution.
 Data extracted from the internal DBMS level is
reformatted to match the user’s external view (e.g.
formatting the results of an SQL query for display
in a Web page)

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 16


Data Independence
The capacity to change the schema at one level of a
database system without having to change the schema at
the next higher level.
Logical Data Independence:

 The capacity to change the conceptual schema without

having to change the external schemas and their


associated application programs.
Physical Data Independence:

 The capacity to change the internal schema without

having to change the conceptual schema.


 For example, the internal schema may be changed

when certain file structures are reorganized or new


indexes are created to improve database performance
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 17

You might also like