1/9/2006 TCSS445A Isabelle Bichindaritz 1

Database Environment
1/9/2006 TCSS445A Isabelle Bichindaritz 2
Learning Objectives
Purpose of three-level database architecture.
Contents of external, conceptual, and internal
levels.
Purpose of external/conceptual and
conceptual/internal mappings.
Meaning of logical and physical data
independence.
Distinction between DDL and DML.
A classification of data models.

1/9/2006 TCSS445A Isabelle Bichindaritz 3
Learning Objectives
Purpose/importance of conceptual modeling.
Typical functions and services a DBMS should
provide.
Software components of a DBMS.
Meaning of clientserver architecture and
advantages of this type of architecture for a DBMS.
Function and uses of Transaction Processing
Monitors.
Function and importance of the system catalog.
1/9/2006 TCSS445A Isabelle Bichindaritz 4
Acknowledgments
These slides have been adapted from Thomas
Connolly and Carolyn Begg
1/9/2006 TCSS445A Isabelle Bichindaritz 5
Objectives of Three-Level
Architecture
All users should be able to access same
data.

A users view is immune to changes made
in other views.

Users should not need to know physical
database storage details.
1/9/2006 TCSS445A Isabelle Bichindaritz 6
Objectives of Three-Level
Architecture
DBA should be able to change database storage
structures without affecting the users views.

Internal structure of database should be
unaffected by changes to physical aspects of
storage.

DBA should be able to change conceptual
structure of database without affecting all users.
1/9/2006 TCSS445A Isabelle Bichindaritz 7
ANSI-SPARC
Three-Level Architecture
1/9/2006 TCSS445A Isabelle Bichindaritz 8
ANSI-SPARC Three-Level
Architecture
External Level
Users view of the database.
Describes that part of database that is relevant to a
particular user.

Conceptual Level
Community view of the database.
Describes what data is stored in database and
relationships among the data.
1/9/2006 TCSS445A Isabelle Bichindaritz 9
ANSI-SPARC Three-Level
Architecture
Internal Level
Physical representation of the database on
the computer.
Describes how the data is stored in the
database.
1/9/2006 TCSS445A Isabelle Bichindaritz 10
Differences between Three Levels
of ANSI-SPARC Architecture
1/9/2006 TCSS445A Isabelle Bichindaritz 11
Data Independence
Logical Data Independence
Refers to immunity of external schemas to
changes in conceptual schema.
Conceptual schema changes (e.g.
addition/removal of entities).
Should not require changes to external
schema or rewrites of application programs.
1/9/2006 TCSS445A Isabelle Bichindaritz 12
Data Independence
Physical Data Independence
Refers to immunity of conceptual schema to
changes in the internal schema.
Internal schema changes (e.g. using different
file organizations, storage structures/devices).
Should not require change to conceptual or
external schemas.
1/9/2006 TCSS445A Isabelle Bichindaritz 13
Data Independence and the
ANSI-SPARC Three-Level
Architecture
1/9/2006 TCSS445A Isabelle Bichindaritz 14
Database Languages
Data Definition Language (DDL)
Allows the DBA or user to describe and
name entities, attributes, and relationships
required for the application
plus any associated integrity and security
constraints.
1/9/2006 TCSS445A Isabelle Bichindaritz 15
Database Languages
Data Manipulation Language (DML)
Provides basic data manipulation operations on
data held in the database.
Procedural DML
allows user to tell system exactly how to manipulate
data.
Non-Procedural DML
allows user to state what data is needed rather than
how it is to be retrieved.
1/9/2006 TCSS445A Isabelle Bichindaritz 16
Database Languages
Fourth Generation Language (4GL)
Query Languages
Forms Generators
Report Generators
Graphics Generators
Application Generators.
1/9/2006 TCSS445A Isabelle Bichindaritz 17
Data Model
Integrated collection of concepts for describing
data, relationships between data, and
constraints on the data in an organization.

Data Model comprises:
a structural part;
a manipulative part;
possibly a set of integrity rules.
1/9/2006 TCSS445A Isabelle Bichindaritz 18
Data Model
Purpose
To represent data in an understandable way.

Categories of data models include:
Object-based
Record-based
Physical.
1/9/2006 TCSS445A Isabelle Bichindaritz 19
Data Models
Object-Based Data Models
Entity-Relationship
Semantic
Functional
Object-Oriented.
Record-Based Data Models
Relational Data Model
Network Data Model
Hierarchical Data Model.
Physical Data Models
1/9/2006 TCSS445A Isabelle Bichindaritz 20
Conceptual Modeling
Conceptual schema is the core of a system
supporting all user views.
Should be complete and accurate representation
of an organizations data requirements.

Conceptual modelling is process of developing a
model of information use that is independent of
implementation details.
Result is a conceptual data model.
1/9/2006 TCSS445A Isabelle Bichindaritz 21
Functions of a DBMS
Data Storage, Retrieval, and Update.

A User-Accessible Catalog.

Transaction Support.

Concurrency Control Services.

Recovery Services.
1/9/2006 TCSS445A Isabelle Bichindaritz 22
Functions of a DBMS
Authorization Services.

Support for Data Communication.

Integrity Services.

Services to Promote Data Independence.

Utility Services.
1/9/2006 TCSS445A Isabelle Bichindaritz 23
Components of a DBMS
1/9/2006 TCSS445A Isabelle Bichindaritz 24
Components of Database
Manager (DM)
1/9/2006 TCSS445A Isabelle Bichindaritz 25
Multi-User DBMS Architectures
Teleprocessing

File-server

Client-server
1/9/2006 TCSS445A Isabelle Bichindaritz 26
Teleprocessing
Traditional architecture.

Single mainframe with a number of
terminals attached.

Trend is now towards downsizing.
1/9/2006 TCSS445A Isabelle Bichindaritz 27
Teleprocessing Topology
1/9/2006 TCSS445A Isabelle Bichindaritz 28
File-Server
File-server is connected to several workstations
across a network.
Database resides on file-server.
DBMS and applications run on each
workstation.
Disadvantages include:
Significant network traffic.
Copy of DBMS on each workstation.
Concurrency, recovery and integrity control more complex.

1/9/2006 TCSS445A Isabelle Bichindaritz 29
File-Server Architecture
1/9/2006 TCSS445A Isabelle Bichindaritz 30
Client-Server
Server holds the database and the
DBMS.
Client manages user interface and runs
applications.
Advantages include:
wider access to existing databases;
increased performance;
possible reduction in hardware costs;
reduction in communication costs;
increased consistency.

1/9/2006 TCSS445A Isabelle Bichindaritz 31
Client-Server Architecture
1/9/2006 TCSS445A Isabelle Bichindaritz 32
Alternative Client-Server Topologies
1/9/2006 TCSS445A Isabelle Bichindaritz 33
Transaction Processing
Monitors
Program that controls data transfer
between clients and servers in order to
provide a consistent environment,
particularly for Online Transaction
Processing (OLTP).
1/9/2006 TCSS445A Isabelle Bichindaritz 34
Transaction Processing Monitor as
middle tier of a three-tier client-
server architecture
1/9/2006 TCSS445A Isabelle Bichindaritz 35
System Catalog
Repository of information (metadata)
describing the data in the database.
Typically stores:
names of authorized users;
names of data items in the database;
constraints on each data item;
data items accessible by a user and the type of access.
Used by modules such as Authorization
Control and Integrity Checker.
1/9/2006 TCSS445A Isabelle Bichindaritz 36
Information Resource Dictionary
System (IRDS)
Response to an attempt to standardize
data dictionary interfaces.

Objectives:
extensibility of data;
integrity of data;
controlled access to data.
1/9/2006 TCSS445A Isabelle Bichindaritz 37
IRDS services interface