Chapter 1

Chapter 1
Database Systems
Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel
In this chapter, you will learn:

The difference between data and information
What a database is, what the different types of
databases are, and why they are valuable assets for decision making The importance of database design How modern databases evolved from file systems
In this chapter, you will learn (continued):

About flaws in file system data management
What the database systems main components
are and how a database system differs from a file system The main functions of a database management system (DBMS)
Data vs. Information

Data:
Raw facts; building blocks of information Unprocessed information
Information:
Data processed to reveal meaning
Accurate, relevant, and timely information is key to
good decision making Good decision making is the key to survival in a global environment
Transforming Raw Data into Information
Transforming Raw Data into Information (continued)
Introducing the Database and the DBMS

Databaseshared, integrated computer structure
that stores:
End user data (raw facts) Metadata (data about data)
Introducing the Database and the DBMS (continued)

DBMS (database management system):
Collection of programs that manages database
structure and controls access to data Possible to share data among multiple applications or users Makes data management more efficient and effective
10
Role and Advantages of the DBMS (continued)

End users have better access to more and better-
managed data
Promotes integrated view of organizations
operations Probability of data inconsistency is greatly reduced Possible to produce quick answers to ad hoc queries
11
Role and Advantages of the DBMS (continued)
12
Types of Databases
Single-user:
Supports only one user at a time
Desktop:
Single-user database running on a personal
computer
Multi-user:
Supports multiple users at the same time
13
Types of Databases (continued)

Workgroup:
Multi-user database that supports a small group of
users or a single department

Enterprise:
Multi-user database that supports a large group of
users or an entire organization
14

Can be classified by location: Centralized:
Supports data located at a single site
Distributed:
Supports data distributed across several sites
15

Can be classified by use: Transactional (or production):
Supports a companys day-to-day operations
Data warehouse:
Stores data used to generate information required
to make tactical or strategic decisions Often used to store historical data Structure is quite different
16
Why Database Design is Important

Defines the databases expected use
Different approach needed for different types of
databases Avoid redundant data Poorly designed database generates errors leads to bad decisions can lead to failure of organization
17
Historical Roots: Files and File Systems

Managing data with file systems is obsolete
Understanding file system characteristics makes
database design easier to understand Awareness of problems with file systems helps prevent similar problems in DBMS Knowledge of file systems is helpful if you plan to convert an obsolete file system to a DBMS
18
Historical Roots: Files and File Systems (continued)

Manual File systems: Collection of file folders kept in file cabinet Organization within folders based on datas expected use (ideally logically related) System adequate for small amounts of data with few reporting requirements Finding and using data in growing collections of file folders became time-consuming and cumbersome
19

Conversion from manual to computer system: Could be technically complex, requiring hiring of data processing (DP) specialists Resulted in numerous home-grown systems being created Initially, computer files were similar in design to manual files (see Figure 1.3)
20
21
22

DP specialist wrote programs for reports:
Monthly summaries of types and amounts of
insurance sold by agents Monthly reports about which customers should be contacted for renewal Reports that analyzed ratios of insurance types sold by agent Customer contact letters summarizing coverage
23

Other departments requested databases be
written for them

SALES database created for sales department AGENT database created for personnel department
24
25

As number of databases increased, small file
system evolved Each file used its own application programs Each file was owned by individual or department who commissioned its creation
26
27
Example of Early Database Design (continued)

As system grew, demand for DPs programming
skills grew Additional programmers hired DP specialist evolved into DP manager, supervising a DP department Primary activity of department (and DP manager) remained programming
28
Problems with File System Data Management

Every task requires extensive programming in a
third-generation language (3GL)

Programmer must specify task and how it must be
done
Modern databases use fourth-generation
languages (4GL)
Allow users to specify what must be done without
specifying how it is to be done
29
30

Time-consuming, high-level activity
As number of files expands, system
administration becomes difficult Making changes in existing file structure is difficult File structure changes require modifications in all programs that use data in that file
31

Modifications are likely to produce errors,
requiring additional time to debug the program Security features hard to program and therefore often omitted
32
Structural and Data Dependence

Structural dependence
Access to a file depends on its structure
33
Structural and Data Dependence (continued)

Data dependence
Changes in the data storage characteristics without
affecting the application programs ability to access the data Logical data format
How the human being views the data
Physical data format How the computer sees the data
34
Field Definitions and Naming Conventions

Flexible record definition anticipates reporting
requirements by breaking up fields into their component parts
35
Field Definitions and Naming Conventions (continued)
36
Data Redundancy
Data redundancy results in data inconsistency
Different and conflicting versions of the same data
appear in different places

Errors more likely to occur when complex entries
are made in several different files and/or recur frequently in one or more files Data anomalies develop when required changes in redundant data are not made successfully
37
Data Redundancy
Types of data anomalies:
Update anomalies
Occur when changes must be made to existing
records
Insertion anomalies
Occur when entering new records
Deletion anomalies
Occur when deleting records
38
Database Systems
Problems inherent in file systems make using a
database system desirable File system

Many separate and unrelated files
Database
Logically related data stored in a single logical data
repository
39
Database Systems
40
The Database System Environment

Database system is composed of five
main
parts:
Hardware Software
Operating system software
DBMS software Application programs and utility software
People
Procedures
Data
41
The Database System Environment (continued)
42
DBMS Functions
DBMS performs functions that guarantee integrity
and consistency of data

Data dictionary management defines data elements and their relationships Data storage management stores data and related data entry forms, report definitions, etc.
43
DBMS Functions (continued)

Data transformation and presentation translates logical requests into commands to physically locate and retrieve the requested data Security management enforces user security and data privacy within database
44

Multiuser access control uses sophisticated algorithms to ensure multiple users can access the database concurrently without compromising the integrity of the database Backup and recovery management provides backup and data recovery procedures Data integrity management promotes and enforces integrity rules
45

Database access languages and application
programming interfaces
provide data access through a query language
Database communication interfaces allow database to accept end-user requests via multiple, different network environments
46
47
48
Summary
Data are raw facts. Information is the result of
processing data to reveal its meaning. To implement and manage a database, use a DBMS. Database design defines the database structure. A well-designed database facilitates data management and generates accurate and valuable information. A poorly designed database can lead to bad decision making, and bad decision making can lead to the failure of an organization.
49
Summary (continued)
Databases were preceded by file systems. Limitations of file system data management:
requires extensive programming system administration complex and difficult making changes to existing structures is difficult
security features are likely to be inadequate

independent files tend to contain redundant data
DBMSs were developed to address file systems
inherent weaknesses
50

Chapter 1

Uploaded by

Copyright:

Available Formats

Chapter 1

Uploaded by

Document Information

Original Description:

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

Chapter 1

Uploaded by

Copyright:

Available Formats

Chapter 1

In this chapter, you will learn:

What a database is, what the different types of

In this chapter, you will learn (continued):

What the database systems main components

Data vs. Information

Accurate, relevant, and timely information is key to

Transforming Raw Data into Information

Transforming Raw Data into Information (continued)

Transforming Raw Data into Information (continued)

Transforming Raw Data into Information (continued)

Introducing the Database and the DBMS

Introducing the Database and the DBMS (continued)

Role and Advantages of the DBMS (continued)

Role and Advantages of the DBMS (continued)

Types of Databases (continued)

users or a single department

users or an entire organization

Types of Databases (continued)

Types of Databases (continued)

Why Database Design is Important

Different approach needed for different types of

Historical Roots: Files and File Systems

Historical Roots: Files and File Systems (continued)

Historical Roots: Files and File Systems (continued)

Historical Roots: Files and File Systems (continued)

Historical Roots: Files and File Systems (continued)

Historical Roots: Files and File Systems (continued)

Historical Roots: Files and File Systems (continued)

written for them

Historical Roots: Files and File Systems (continued)

Historical Roots: Files and File Systems (continued)

Historical Roots: Files and File Systems (continued)

Example of Early Database Design (continued)

Problems with File System Data Management

third-generation language (3GL)

specifying how it is to be done

Problems with File System Data Management

Problems with File System Data Management

As number of files expands, system

Problems with File System Data Management

Structural and Data Dependence

Structural and Data Dependence (continued)

Physical data format How the computer sees the data

Field Definitions and Naming Conventions

requirements by breaking up fields into their component parts

Field Definitions and Naming Conventions (continued)

appear in different places

database system desirable File system

The Database System Environment

The Database System Environment (continued)

and consistency of data

DBMS Functions (continued)

DBMS Functions (continued)

DBMS Functions (continued)

DBMS Functions (continued)

DBMS Functions (continued)

security features are likely to be inadequate

DBMSs were developed to address file systems