Lecture - 1

The Database Environment

 Definitions
• Data: stored representations of meaningful objects
and events
• Structured: numbers, text, dates
• Unstructured: images, video, documents

• Information: processed data to increase knowledge

• Metadata: data that describes the properties and
context of user data
Figure 1: a Data in context

Context helps users understand data

 Figure 2: Metadata for class Roster

Descriptions of the properties or characteristics of the data,

including data types, field sizes, allowable values, and data context
 The Database Approach
Database is:
• Organized collection of logically related data

• Central repository of shared data

• Data is managed by a controlling agent

• Stored in a standardized and convenient form called Database

• Requires a Database Management System (DBMS)

 Figure 4: Database Management System
 A software system that is used to create, maintain, and
provide controlled access to user databases
Order Filing
System

Invoicing Central database

DBMS
System
Contains employee,
order, inventory,
Payroll pricing, and
System customer data

DBMS manages data resources like as an operating system

manages hardware resources
Figure 5: Database Architecture System
• Application program
• Accesses database by sending
queries to DBMS
• Manipulating a database
• Update the database
• Generate reports
• Meta-data
• Database of descriptive
information Stored and managed
by DBMS in the form of a
 Advantages of Database Approach
• Improved data sharing
• Multiple users and programs can access the database simultaneously
• Support Multiple Views for Data
• View is a Subset of the database
• Virtual data that is not explicitly stored can be derived from the database
• Multiuser DBMS
• Users have a variety of distinct applications
• Protection:
• Including the System protection and Security protection to restrict the
unauthorized access
• Concurrency control software
Ensure that several users able to update the same data, must performed in a
 Database classification on data Types
• Traditional database applications
- Store textual or numeric information
• Multimedia databases
- Store images, audio clips, and digital video stream
• Geographic information systems (GIS)
- Store and analyze maps, weather data, and satellite images
• Real-time and active database technology
- Control industrial and manufacturing processes
• Data warehouses and online analytical processing (OLAP) systems
- Extract and analyze useful business information from very large databases
- Support decision making
Figure 6: Components of Database Environment
 Components of Database Environment
• CASE Tools: computer-aided software engineering (case tool as
computer-aided design (CAD) used to design hardware product
• Repository: centralized storehouse of metadata
• Database: storehouse of the data
• Database Management System (DBMS): software for managing
the database
• Application Programs: software using the data
• User Interface: text and graphical form that are displayed to the users
 Actors on the Scene
PEOPLE THAT WORK WITH DATABASES
- System Analysts
- Database Designers
- Application Developers
- Database Administrators
- End Users
 System Analysts
• Communicate with each of the prospective database user group
in order to understand its
• Information needs
• Processing needs
• Develop a specification of each user group’s information and
processing needs
• Develop a specification of integrating the information and
processing needs of the user groups
• Document the specification
 Database Designers
Choose appropriate structures to:
• Represent the information specified by the system analysts

• Store the information in a normalized manner in order to

guarantee integrity and consistency of data

• Guarantee an efficient system

• Document the database design

 Application Developers
• Implement the database design

• Implement the application programs to meet the

program specifications

• Test and debug the database implementation and the

application programs

• Document the database implementation and the

application programs
 Database Administrators
• Manage the database management system
• Generate database application performance reports
• Investigate user performance complaints
• Assess need for changes in database structure/application
design
• Modify database structure
• Develop and train staff on backup and recovery procedures
Database Management System Architecture
• Teleprocessing Database

• File-Sharing Database

• Client-Server Database - Basic

• Client-Server Database - w/Caching

• Distributed Database

• Multi-Database

• Parallel Databases
 TELEPROCESSING DATABASE
Micro terminal Micro terminal Micro terminal

Phone
• Dumb terminals (just monitors)
communication lines
are micro terminals
OSTP

AP1 AP2 AP3 mainframe

• APs, DBMS, and DB reside on
central computer DBMS

OSDB
• Communication lines are phone
lines
DB database
• Screen formatting are transmitted
 File-Sharing Database
• Aps and DBMS on micros clients
(PCs) AP1 AP2 AP3
Clients
• File-Server on micro server DBMS DBMS
• Clients and file-server communicate OSNET OSNET
via LAN
Clients and file server
• High traffic on LAN. So, files must be connected via LAN
sent to DBMS on clients for processing
OSNET Micro
• Extensive lock contention for extended server
OSDB
periods of time for the same request
• Good for extensive query processing
for downloaded snapshot data DB
 Client-Server Database - Basic
- The client requests services from a server that performs the required
services and returns the results to the client.
• Application Programs run on the client PCs
• DBMS playing its role on a server. AP1 AP2 AP3
OSNET OSNET
• Multiple servers allowed without
LAN
data replication
OSNET
• Clients and database-server Micro(s) or
DBMS
Mainframe
communicate via LAN OSDB
• less traffic on LAN and less lock
Database
contention than with file-server DB
 Client-Server Database: with Caching
• DBMS on server and clients DBMS for
queries
• Database-server is primary update site update
AP1 AP2 AP3
• Downloaded queries are cached on micros
clients DBMS DBMS
OSNET OSNET
• Cached queries are updated
incrementally
LAN
• Less traffic on LAN than with basic DB DB
client-server database because the OSNET
micro(s) or
initial query result is only downloaded DBMS
mainframe
• Less lock contention than with basic OSDB
DBMS
client-server database for same reason for sit
updat
e Data base
DB
 Two-tier client-server Architecture
• User Interface Programs and Application Programs run on the client side
• Interface Programs called ODBC (Open Database Connectivity):
- Provides an Application program interface (API) allow client programs to
call the DBMS.
- Most DBMS vendors provide ODBC drivers.

application
program

ODBC
Interface
 Three-tier client-server Architecture
• Common for Web applications (Web applications server)
• Intermediate Layer called Application Server or Web Server
• stores the web connectivity software to access the right amount of data from the
database server
• acts like a channel for sending partially processed data between the database server and
the client.
• Three-tier Additional Features- Security:
• encrypt the data at the server before transmission
• decrypt data at the client
 Distributed Database
• One database distributed on multi storage AP1 AP2 AP3
micros(s) or
• APs and DDBMS on multiple micros DDBMS DDBMS mainframes

OSNET&DB OSNET&DB
Communication via LAN or WAN
network
• Fragmentation and replication are
allowed and performed in transparence external external external
mnner
conceptual
• Data replication improves query
processing internal

• Data replication increases lock contention

and slows down update transactions DB 1 DB 2 DB 3
 Multi Database
• A multi-database is a distributed
AP1 AP2 AP3
database without a shared schema micros(s
MULTI-DBMS MULTI-DBMS
) or
• The same language is used for OSNET&DB OSNET&DB mainfra
different APs to access multiple mes
databases using multi-DBMS
• A multi-DBMS accesses other Schema 1 Schema 2 Schema 3
databases via a network, like the conceptual1 conceptual2 conceptual3
www
internal1 internal2 internal3
• Participants in a multi-database
may respond to query and update
requests from other participants DB DB DB
 Parallel Database
• A database in which a single query may be executed by
multiple processors working together in parallel
• There are three types of systems:
• Shared memory
• Shared disk
• Shared nothing
Parallel Databases - Shared Memory
• Multiple processors share memory via bus
P
M • The processors communication via memory
P wire
• bus becomes the bottleneck
P
• not scalable beyond 32 or 64 processors
P

P processor

M memory

disk
 Parallel Databases - Shared Disk
• processors share disk via interconnection
P network
M
• memory bus not a bottleneck
M P
• fault tolerance wrt. processor or memory failure
M P • scales better than shared memory
• interconnection network to disk subsystem is a
M P
bottleneck
• used in Oracle DB
Parallel Databases - Shared Nothing

M P • scales better than shared memory and shared disk

• main drawbacks:
• higher processor communication cost
M P
• higher cost of non-local disk access
• used in the Teradata database machine
M P

M P