Scribd
Upload
17 views16 pages

Chapter 02

The document discusses key concepts in database systems including data models, schemas, and architecture. It defines a data model as a set of concepts that describe database structure, operations, and constraints. A database schema represents the description of a database including structure and constraints, while a database state refers to the actual data stored at a point in time. The three-schema architecture separates schemas at the internal, conceptual, and external levels to support independence between levels.

Uploaded by

mba20238
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
17 views16 pages

Chapter 02

The document discusses key concepts in database systems including data models, schemas, and architecture. It defines a data model as a set of concepts that describe database structure, operations, and constraints. A database schema represents the description of a database including structure and constraints, while a database state refers to the actual data stored at a point in time. The three-schema architecture separates schemas at the internal, conceptual, and external levels to support independence between levels.

Uploaded by

mba20238
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/ 16

CHAPTER 2

Database System Concepts


and Architecture

Copyright © 2017 Ramez Elmasri and Shamkant B. Navathe Slide 1- 1


Data Models
 Data Model:
 A set of concepts to describe the structure of a database,
the operations for manipulating these structures, and
certain constraints that the database should obey.
 Data Model Structure and Constraints:
 Constructs are used to define the database structure
 Constructs typically include elements (and their data
types) as well as groups of elements (e.g. entity, record,
table), and relationships among such groups
 Constraints specify some restrictions on valid data; these
constraints must be enforced at all times

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


Data Models (continued)
 Data Model Operations:
 These operations are used for specifying database
retrievals and updates by referring to the
constructs of the data model.
 Operations on the data model may include basic
model operations (e.g. generic insert, delete,
update) and user-defined operations (e.g.
compute_student_gpa, update_inventory)

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


Schemas versus Instances
 Database Schema:
 The description of a database.
 Includes descriptions of the database structure,
data types, and the constraints on the database.
 Schema Diagram:
 An illustrative display of (most aspects of) a
database schema.
 Schema Construct:
 A component of the schema or an object within
the schema, e.g., STUDENT, COURSE.

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


Schemas versus Instances
 Database State:
 The actual data stored in a database at a
particular moment in time. This includes the
collection of all the data in the database.
 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 © 2017 Ramez Elmasri and Shamkant B. Navathe Slide 2- 5


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 © 2017 Ramez Elmasri and Shamkant B. Navathe Slide 2- 6


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.


 State is also called extension.

Copyright © 2017 Ramez Elmasri and Shamkant B. Navathe Slide 2- 7


Example of a Database Schema

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


Example of a database state

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


Three-Schema Architecture
 Proposed to support DBMS characteristics of:
 Program-data independence.
 Support of multiple views of the data.
 Not explicitly used in commercial DBMS products,
but has been useful in explaining database
system organization

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


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 © 2017 Ramez Elmasri and Shamkant B. Navathe Slide 2- 11


The three-schema architecture

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


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 © 2017 Ramez Elmasri and Shamkant B. Navathe Slide 2- 13


Data Independence
 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 © 2017 Ramez Elmasri and Shamkant B. Navathe Slide 2- 14


Data Independence (continued)
 When a schema at a lower level is changed, only
the mappings between this schema and higher-
level schemas need to be changed in a DBMS
that fully supports data independence.
 The higher-level schemas themselves are
unchanged.
 Hence, the application programs need not be
changed since they refer to the external schemas.

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


Classification of DBMSs
 Based on the data model used
 Legacy: Network, Hierarchical.
 Currently Used: Relational, Object-oriented, Object-
relational
 Recent Technologies: Key-value storage systems,
NOSQL systems: document based, column-based,
graph-based and key-value based. Native XML DBMSs.
 Other classifications
 Single-user (typically used with personal computers)
vs. multi-user (most DBMSs).
 Centralized (uses a single computer with one database)
vs. distributed (multiple computers, multiple DBs)

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

You might also like