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
Schemas, Instances, and States
Three-Schema Architecture
Data Independence
DBMS Languages and Interfaces
Database System Utilities and Tools
Classification of DBMSs
History of Data Models
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 3
Data Models
Data Abstraction:
The suppression of details of data organization
and storage
g and the highlighting
g g g of essential
features for better understanding
Data Model:
A set of concepts to describe the structure of a
database, and certain constraints that the
database should obey
obey.
Data model helps to achieve data abstraction.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 4
Categories of Data Models
Conceptual (high-level, semantic) data models:
Provide
P id concepts that
h are close
l to the
h way many users perceive
i
data.
Also called entity-based or object-based data models.
Physical (low
(low-level,
level, internal) data models:
Provide concepts that describe details of how data is stored in the
computer.
Representational (Implementation) data models:
Provide concepts that may be understood by end users but that
are not too different from the way data is organized within the
computer
Hide some details of data storage but can be implemented on a
computer system in a direct way
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
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 a database schema.
Schema Construct:
A component of the schema or an object within the
schema, e.g., STUDENT, COURSE.
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.
Al called
Also ll d d
database
t b iinstance
t ((or occurrence or snapshot).
h t)
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 6
Database Schema vs
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 initiallyy loaded into
the system.
Valid State:
A state that satisfies the structure and constraints of the
database.
Schema and State Distinction
The database schema changes g veryy infrequently.
q y The
database state changes every time the database is
updated.
Schema is also called intension whereas State is also
called extension.
extension
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
Example of a database state
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 9
Three Schema Architecture
Three-Schema
Proposed to help achieve the DB characteristics
Specially
S i ll to separate user applications
li i andd the
h physical
h i ld database
b
It defines DBMS schemas at three levels:
Internal schema at the internal level to describe physical storage
structures and access paths (e([Link] indexes)
indexes).
Typically uses a physical data model.
Conceptual schema at the conceptual level to describe the
structure for the whole database for a community of users. It hides
th d
the details
t il off th
the physical
h i l storage
t structures
t t and
d concentrates
t t on
describing entities, data types, relationships, and constraints.
Uses a conceptual or an implementation data model.
External schemas at the external level to describes the p part of
the database that a particular user group is interested in and hides
the rest of the database from that user group.
Usually uses the same data model as the conceptual schema.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 10
The three
three-schema
schema architecture
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 11
Data Independence
The ability
y to change
g the schema at one level of the
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
li ti programs.
Physical Data Independence:
The capacity to change the internal schema without having to
change the conceptual schema.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 12
DBMS Languages
Data Definition Language (DDL): a language that is used to define
database schemas. The DDL statement is used to identify description
of the schema construct and store the schema description in the
DBMS catalog.
Data Manipulation Language (DML): a language that is used to
manipulate (retrieve, insert, delete, and modify) data.
A high-level or non-procedural DML can be used on its own to
specify complex database operations in a concise manner, such
as SQL.
A low-level or procedural DML typically retrieves individual
records or objects from the database and processes each
separately, such as PL/SQL.
Embedded Languages: DML with Java, VB, C++, etc.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 13
DBMS Interfaces
Stand-alone q
query
y language
g g interfaces
Example: Entering SQL queries at the DBMS interactive
SQL interface (such as, SQL*Plus in ORACLE)
Programmer interfaces for embedding DML in
programming languages
User-friendly interfaces
Menu-based,
M b d popular
l ffor b
browsing
i on th the webb
Forms-based, designed for naïve users
Graphics-based
Natural language: requests in written English
Parametric interfaces, e.g., bank tellers using function keys.
Interfaces for the DBA
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 14
DBMS Component Modules
A typical
yp DBMS consists of the following
g components:
p
DDL compiler: process schema definitions, specified in the
DDL statements, and stores descriptions of the schemas in
the system
y catalog.
g
DML compiler: compiles the DML commands into object
code for database access.
Run-time
Run time database processor: handles database access at
run time. It receives retrieval and update operations and
carries them out on the database.
Queryy compiler:
Que co p e handles
a d es high-level
g e e quequeries
es tthat
at a
are
eeentered
te ed
interactively.
Data manager: controls access to DBMS information that is
stored on disk throughg interaction with operating
p g system.
y
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 15
DBMS Component modules
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 16
Database System Utilities
There are some functions that are not pprovided through
g
the normal DBMS components rather they are provided
through additional programs called utilities. Some of these
are:
Loading or import utility: used to load or import existing data
files into the database.
Backup utility: used to create backup copies of the
database, usually by dumping the entire database onto
tape.
File reorganization utility: is used to reorganize a database
file into a different file organization to improve performance.
Performance monitoring utility: is used to monitor database
usage and provides statistics to the DBA.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 17
Other Tools
Data dictionary / repository:
Used to store schema descriptions and other information such as
design decisions, application program descriptions, user
information, etc.
CASE tools:
Used in the design phase of database
E
Examples:
l R
Rational
ti lRRose, TOAD
Application Development Environments:
Provides
P id ffacilities
iliti ffor d
developing
l i d database
t b applications
li ti iincluding
l di
database design, graphical user interface development, querying
and updating, and application program development.
PowerBuilder (Sybase)
(Sybase), JBuilder (Borland)
(Borland), JDeveloper 10G (Oracle)
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 18
Classification of DBMSs
Several criteria are normally used to classify DBMSs
Data Model:
Relational, Object, Object-Relational, Hierarchical, Network
Number of Users:
Single-user system
Multi-user system
Number of Sites
Distributed
Centralized
Cost:
P
Purpose:
General
special
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 19
History of Data Models
Network Model:
The first network DBMS was implemented by Honeywell in
1964-65 (IDS System). Later implemented in a large variety
of systems
Hi
Hierarchical
hi l Data
D t Model:
M d l
Used in IBM’s IMS (and some other products) which still
have a large customer base worldwide.
Dominated the DBMS market during 1965
1965-1985
1985
Relational Model:
Proposed in 1970 by E.F. Codd (IBM), first commercial
system in 1981
1981-82.
82 Currently most dominant.
dominant
In several commercial and free open source products:
DB2, ORACLE, MS SQL Server, SYBASE, INFORMIX.
MySQL PostgreSQL
MySQL,
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 20
History of Data Models
Object-oriented
j Data Models:
Comprises models of persistent O-O Programming
Languages such as C++ (e.g., in OBJECTSTORE), Java
and Smalltalk (e
(e.g.,
g in GEMSTONE)
GEMSTONE).
Object-Relational Models:
Most Recent Trend. Started with Informix Universal Server.
Relational systems incorporate concepts from object
databases leading to object-relational.
Exemplified in the latest versions of Oracle
Oracle-10i,
10i DB2
DB2, and
SQL Server and other DBMSs.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 21
