The Database Environment

Chapter 1:
The Database Environment

Modern Database Management
6th Edition
Jeffrey A. Hoffer, Mary B. Prescott, Fred R.
McFadden
Prentice Hall, 2002
Definitions
Data:
Meaningful facts, text, graphics,

images, sound, video segments
Database: An organized collection of
logically related data
Information: Data processed to be useful in
decision making
Metadata: Data that describes data
Chapter 1
Prentice Hall, 2002
Figure 1-1a Data in Context
Large volume of facts,

difficult to interpret or
make decisions based on
Chapter 1
Prentice Hall, 2002
Figure 1-1b Summarized data

Useful information that managers
can use for decision making and
interpretation
Chapter 1
Prentice Hall, 2002
Table 1-1 Metadata

Descriptions of the properties or
characteristics of the data, including data
types, field sizes, allowable values, and
documentation
Chapter 1
Prentice Hall, 2002
Disadvantages of File Processing

Program-Data
Dependence
All programs maintain metadata for each file they use
Data
Redundancy (Duplication of data)
Different systems/programs have separate copies of the same data
Limited
Data Sharing
No centralized control of data
Lengthy
Development Times
Programmers must design their own file formats
Excessive
Program Maintenance
80% of of information systems budget
Chapter 1
Prentice Hall, 2002
Figure 1-2 Three file processing systems at Pine

Valley Furniture
Duplicate
Data
Chapter 1
Prentice Hall, 2002
Problems with Data Dependency
Each application programmer must maintain their

own data
Each application program needs to include code
for the metadata of each file
Each application program must have its own
processing routines for reading, inserting, updating
and deleting data
Lack of coordination and central control
Non-standard file formats
Chapter 1
Prentice Hall, 2002
Problems with Data

Redundancy
Waste
of space to have duplicate data

Causes more maintenance headaches
The biggest Problem:
When data changes in one file, could cause
inconsistencies
Compromises data integrity
Chapter 1
Prentice Hall, 2002
SOLUTION:
The DATABASE Approach
Central
repository of shared data

Data is managed by a controlling agent
Stored in a standardized, convenient
form
Requires a Database Management System (DBMS)
Chapter 1
Prentice Hall, 2002
10
Database Management
System
A DBMS
is a data storage and retrieval

system which permits data to be stored nonredundantly while making it appear to the
user as if the data is well-integrated.
Chapter 1
Prentice Hall, 2002
11
Application
#1
Application
#2
Application
#3
Chapter 1
Database Management
System
DBMS
Database
containing
centralized
shared data
DBMS manages data

resources like an operating
system manages hardware
resources
Prentice Hall, 2002
12
Advantages of Database Approach

Program-Data
Independence
Metadata stored in DBMS, so applications dont need to worry
about data formats

Data queries/updates managed by DBMS so programs dont
need to process data access routines
Results in increased application development and maintenance
productivity
Minimal
Data Redundancy
Leads to increased data integrity/consistency
Chapter 1
Prentice Hall, 2002
13
Advantages of Database Approach

Improved
Data Sharing
Different users get different views of the data
Enforcement
of Standards
All data access is done in the same way
Improved
Data Quality
Constraints, data validation rules
Better
Data Accessibility/ Responsiveness
Use of standard data query language (SQL)
Security, Backup/Recovery, Concurrency

Disaster recovery is easier
Chapter 1
Prentice Hall, 2002
14
Costs and Risks of the

Database Approach
Up-front
costs:
Installation Management Cost and Complexity

Conversion Costs
Ongoing
Costs
Requires New, Specialized Personnel

Need for Explicit Backup and Recovery
Organizational
Conflict
Old habits die hard

Chapter 1
Prentice Hall, 2002
15
Figure 1-3 Segment from enterprise data

Figure
3
model
Chapter 1
Prentice Hall, 2002
16

model
Figure
3
One customer may place many

orders, but each order is placed
by a single customer
One-to-many relationship
Chapter 1
Prentice Hall, 2002
17

Figure
3
model
One order has many order

lines; each order line is
associated with a single order
Chapter 1
Prentice Hall, 2002
18

Figure
3
model
One product can be in many

order lines, each order line refers
to a single product
Chapter 1
Prentice Hall, 2002
19

Figure
3
model
Therefore, one order involves

many products and one product
is involved in many orders
Many-to-many relationship
Chapter 1
Prentice Hall, 2002
20
Figure 1-4 Order, Order_Line, Customer, and Product tables

Relationships established in special columns that provide links
between tables
Chapter 1
Prentice Hall, 2002
21
Figure 1-5
Client/server
system for
Pine Valley
Furniture
Company
Chapter 1
Prentice Hall, 2002
22
Figure 1-6 Customer invoice (Pine Valley Furniture Company)

Application program functions:
inserting new data, updating existing data,
deleting existing data, reading data for display
Chapter 1
Prentice Hall, 2002
23
The Range of
Database Applications
Personal
Database standalone desktop database

Workgroup Database local area network (<25 users)
Department Database local area network (25-100 users)
Enterprise Database wide-area network (hundreds or
thousands of users)
Chapter 1
Prentice Hall, 2002
24
Figure 1-7
Typical data
from a
personal
computer
database
Chapter 1
Prentice Hall, 2002
25
Figure 1-8 Workgroup database with local area network
Chapter 1
Prentice Hall, 2002
26
Figure 1-9 An
enterprise
data
warehouse
Chapter 1
Prentice Hall, 2002
27
Components of the
Database Environment
CASE Tools computer-aided software engineering

Repository centralized storehouse of metadata
Database Management System (DBMS) software for managing the
database
Database storehouse of the data
Application Programs software using the data
User Interface text and graphical displays to users
Data Administrators personnel responsible for maintaining the
database
System Developers personnel responsible for designing databases
and software
End Users people who use the applications and databases
Chapter 1
Prentice Hall, 2002
28
Figure 1-10
Components
of the
database
environment
Chapter 1
Prentice Hall, 2002
29
Evolution of DB Systems
Flat
files - 1960s - 1980s

Hierarchical 1970s - 1990s
Network 1970s - 1990s
Relational 1980s - present
Object-oriented 1990s - present
Object-relational 1990s - present
Data warehousing 1980s - present
Web-enabled 1990s - present
Chapter 1
Prentice Hall, 2002
30

The Database Environment

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

The Database Environment

Uploaded by

Copyright:

Available Formats

Chapter 1:

The Database Environment

Prentice Hall, 2002

Meaningful facts, text, graphics,

Prentice Hall, 2002

Figure 1-1a Data in Context

Large volume of facts,

Prentice Hall, 2002

Figure 1-1b Summarized data

Prentice Hall, 2002

Table 1-1 Metadata

Prentice Hall, 2002

Disadvantages of File Processing

All programs maintain metadata for each file they use

Redundancy (Duplication of data)

Different systems/programs have separate copies of the same data

No centralized control of data

Programmers must design their own file formats

80% of of information systems budget

Prentice Hall, 2002

Figure 1-2 Three file processing systems at Pine

Prentice Hall, 2002

Problems with Data Dependency

Each application programmer must maintain their

Prentice Hall, 2002

Problems with Data

of space to have duplicate data

Prentice Hall, 2002

repository of shared data

Prentice Hall, 2002

is a data storage and retrieval

Prentice Hall, 2002

DBMS manages data

Prentice Hall, 2002

Advantages of Database Approach

Metadata stored in DBMS, so applications dont need to worry

about data formats

Leads to increased data integrity/consistency

Prentice Hall, 2002

Advantages of Database Approach

Different users get different views of the data

All data access is done in the same way

Constraints, data validation rules

Data Accessibility/ Responsiveness

Use of standard data query language (SQL)

Security, Backup/Recovery, Concurrency

Prentice Hall, 2002

Costs and Risks of the

Installation Management Cost and Complexity

Requires New, Specialized Personnel

Old habits die hard

Prentice Hall, 2002

Figure 1-3 Segment from enterprise data

Prentice Hall, 2002

Figure 1-3 Segment from enterprise data

One customer may place many

Prentice Hall, 2002

Figure 1-3 Segment from enterprise data

One order has many order

Prentice Hall, 2002

Figure 1-3 Segment from enterprise data

One product can be in many

Prentice Hall, 2002