Database Management Systems

ANKIT RAJPAL

1
 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

2
Transforming Raw Data into
Information

3
Transforming Raw Data into
Information (continued)

4
Transforming Raw Data into
Information (continued)

5
Transforming Raw Data into
Information (continued)

6
 Introducing the Database
and the DBMS
 Database—shared, integrated computer structure that
stores:
 End user data (raw facts)
 Metadata (data about data)

7
 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

8
Role and Advantages of the DBMS
(continued)
 End users have better access to more and better-
managed data
 Promotes integrated view of organization’s operations
 Probability of data inconsistency is greatly reduced
 Possible to produce quick answers to ad hoc queries

9
Role and Advantages of the
DBMS (continued)

10
 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

11
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

12
Types of Databases (continued)
Can be classified by location:
 Centralized:
 Supports data located at a single site
 Distributed:
 Supports data distributed across several sites

13
Types of Databases (continued)
Can be classified by use:
 Transactional (or production):
 Supports a company’s 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

14
Why Database Design is Important
 Defines the database’s 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

15
 Historical Roots: Files and File
Systems
Manual File systems:
 Collection of file folders kept in file cabinet
 Organization within folders based on data’s 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

16
 Historical Roots: Files and File
Systems
(continued)
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)

17
Historical Roots: Files and File Systems
(continued)

18
 Historical Roots: Files and File
Systems
(continued)
 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

19
 Historical Roots: Files and File
Systems
(continued)
 Other departments requested databases be written for
them
 SALES database created for sales department
 AGENT database created for personnel department

20
Historical Roots: Files and File Systems
(continued)

21
Historical Roots: Files and File Systems
(continued)

22
Example of Early Database Design
(continued)
 As system grew, demand for DP’s 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

23
 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

24
Problems with File System
Data Management

25
 Problems with File System
Data Management
 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

26
 Problems with File System
Data Management
 Modifications are likely to produce errors, requiring
additional time to “debug” the program
 Security features hard to program and therefore often
omitted

27
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

28
Database Systems

29
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

30
The Database System Environment (continued)

31
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.

32
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

33
DBMS Functions (continued)
 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

34
DBMS Functions (continued)
 Database access languages and application
programming interfaces
 provide data access through a query language

 Database communication interfaces

35
DBMS Functions (continued)

36
Three-Schema Architecture

37
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.

38
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
 DBMS’s were developed to address file systems’ inherent
weaknesses

39