Database Security

CT069-3-3

Database Architecture
 Topic and Structure of Lesson

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.

Module Code and Module Title Title of Slides Slide 2 (of 44)
 Topic and Structure of Lesson (2)

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.

Module Code and Module Title Title of Slides Slide 3 (of 44)
 Learning Outcomes

At the end of this lesson, YOU should be able to:

explain the purpose of three-level database architecture.

explain the meaning of clientserver architecture and advantages of

this type of architecture for a DBMS.

discuss the contents of external, conceptual, and internal levels.

discuss the purpose of external/conceptual and conceptual/internal

mappings.

explain the meaning of logical and physical data independence.

discuss the function and importance of the system catalogue.

Module Code and Module Title Title of Slides Slide 4 (of 44)
 Key Terms you must be able to use

If you have mastered this topic, you should be able to

use the following terms correctly in your assignments
and exams:

Data Independence
External View
Conceptual View
Physical View

Module Code and Module Title Title of Slides Slide 5 (of 44)
 Objectives of 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.

Module Code and Module Title Title of Slides Slide 6 (of 44)
 Objectives of Architecture (2)

DBA should be able to change database

storage structures without affecting the users
views.

Module Code and Module Title Title of Slides Slide 7 (of 44)
 Objectives of Architecture (3)

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.

Module Code and Module Title Title of Slides Slide 8 (of 44)
 ANSI-SPARC Architecture

Module Code and Module Title Title of Slides Slide 9 (of 44)
 ANSI-SPARC Architecture (2)

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.

Module Code and Module Title Title of Slides Slide 10 (of 44)
 ANSI-SPARC Architecture (3)

Internal Level
Physical representation of the database on the
computer.
Describes how the data is stored in the database.

Module Code and Module Title Title of Slides Slide 11 (of 44)
 ANSI-SPARC Architecture (4)

Module Code and Module Title Title of Slides Slide 12 (of 44)
 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

Module Code and Module Title Title of Slides Slide 13 (of 44)
 Data Independence (2)

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

Module Code and Module Title Title of Slides Slide 14 (of 44)
 Data Independence (3)

Module Code and Module Title Title of Slides Slide 15 (of 44)
 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

Module Code and Module Title Title of Slides Slide 16 (of 44)
 Database Languages (2)

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

Module Code and Module Title Title of Slides Slide 17 (of 44)
 Database Languages (3)

Fourth generation language (4GL)

Query languages
Forms generators
Report generators
Graphics generators
Application generators

Module Code and Module Title Title of Slides Slide 18 (of 44)
 Functions of DBMS

Data storage, retrieval, and update.

A user-accessible catalogue.

Transaction support.

Concurrency control services.

Recovery services.

Module Code and Module Title Title of Slides Slide 23 (of 44)
 Functions of DBMS (2)

Authorization services.

Support for data communication.

Integrity services.

Services to promote data independence.

Utility services.

Module Code and Module Title Title of Slides Slide 24 (of 44)
 Components of DBMS

Module Code and Module Title Title of Slides Slide 25 (of 44)
Module Code and Module Title Title of Slides #
 Multi-user DBMS Architecture

Teleprocessing

File-server

Client-server

Module Code and Module Title Title of Slides Slide 27 (of 44)
 Teleprocessing Architecture

Traditional architecture.

Single mainframe with a number of terminals

attached.

Trend is now towards downsizing.

Module Code and Module Title Title of Slides Slide 28 (of 44)
 Teleprocessing Architecture (2)

Module Code and Module Title Title of Slides Slide 29 (of 44)
 File Server Architecture

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.

Module Code and Module Title Title of Slides Slide 30 (of 44)
 File Server Architecture (2)

Module Code and Module Title Title of Slides Slide 31 (of 44)
 Client Server Architecture

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.

Module Code and Module Title Title of Slides Slide 32 (of 44)
 Client Server Architecture (2)

Module Code and Module Title Title of Slides Slide 33 (of 44)
 Client Server Architecture (3)

Module Code and Module Title Title of Slides Slide 34 (of 44)
 Quick Review Questions
What is metadata?

List any FIVE functions in a DBMS.

List and explain any five major components of a

database manager.

List and explain three types of multi user database

system architectures.

Module Code and Module Title Title of Slides Slide 40 (of 44)
 Follow Up Assignment

We learnt only the concepts of database

architecture.

Conduct further research on the architecture of

client server database architectures.

Module Code and Module Title Title of Slides Slide 41 (of 44)
 Summary

ANSI-SPARC Database Architecture

DBMS Functions

DBMS Components

Multi User DBMS Architecture

Module Code and Module Title Title of Slides Slide 42 (of 44)
 Question and Answer Session

Q&A

Module Code and Module Title Title of Slides Slide 43 (of 44)
 Next Session

Entity Relationship Modeling

Module Code and Module Title Title of Slides Slide 44 (of 44)