Database Management System

35
1 Database Management Database Management System System

description

Database Management System. 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 - PowerPoint PPT Presentation

Transcript of Database Management System

Page 1: Database Management System

1

Database Management SystemDatabase Management System

Page 2: Database Management System

2

DefinitionsDefinitions 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 Database management system (DBMS) is a software

application that stores the structure of the database, the data itself, relationships among data in the database, and forms and reports pertaining to the database.

Page 3: Database Management System

3

Figure 1-1a Data in Context

Large volume of facts, difficult to interpret or make decisions based on

Page 4: Database Management System

4

Figure 1-1b Summarized data

Useful information that managers can use for decision making and interpretation

Page 5: Database Management System

5

Table 1-1 MetadataDescriptions of the properties or characteristics of the data, including data types, field sizes, allowable values, and documentation

Page 6: Database Management System

6

Disadvantages of File ProcessingDisadvantages of File ProcessingProgram-Data Dependence

– All programs maintain metadata for each file they useData Redundancy (Duplication of data)

– Different systems/programs have separate copies of the same dataLimited Data Sharing

– No centralized control of dataLengthy Development Times

– Programmers must design their own file formatsExcessive Program Maintenance

– 80% of of information systems budget

Page 7: Database Management System

7

Figure 1-2 Three file processing systems at Pine Valley Furniture

Duplicate Data

Page 8: Database Management System

8

Problems with Data DependencyProblems 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

Page 9: Database Management System

9

Problems with Data Problems with Data RedundancyRedundancy

Waste of space to have duplicate dataCauses more maintenance headachesThe biggest Problem:

– When data changes in one file, could cause inconsistencies

– Compromises data integrity

Page 10: Database Management System

10

SOLUTION: SOLUTION: The DATABASE ApproachThe DATABASE Approach

Central repository of shared dataData is managed by a controlling agentStored in a standardized, convenient

form

Requires a Database Management System (DBMS)

Page 11: Database Management System

11

Database Management Database Management SystemSystem

A DBMS is a data storage and retrieval system which permits data to be stored non-redundantly while making it appear to the user as if the data is well-integrated.

Page 12: Database Management System

12

Database Management Database Management SystemSystem

DBMS manages data resources like an operating system manages hardware resources

DBMS Databasecontainingcentralized

shared data

Application#1

Application#2

Application#3

Page 13: Database Management System

13

Advantages of Database Approach Advantages of Database Approach

Program-Data Independence – Metadata stored in DBMS, so applications don’t need to worry

about data formats– Data queries/updates managed by DBMS so programs don’t

need to process data access routines– Results in: increased application development and maintenance

productivityMinimal Data Redundancy

– Leads to increased data integrity/consistency

Page 14: Database Management System

14

Advantages of Database ApproachAdvantages of Database ApproachImproved Data Sharing

– Different users get different views of the dataEnforcement of Standards

– All data access is done in the same wayImproved Data Quality

– Constraints, data validation rulesBetter Data Accessibility/ Responsiveness

– Use of standard data query language (SQL)Security, Backup/Recovery, Concurrency

– Disaster recovery is easier

Page 15: Database Management System

15

Costs and Risks of the Costs and Risks of the Database ApproachDatabase 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

Page 16: Database Management System

16

Elements of the Database Elements of the Database ApproachApproach

Data models – Graphical system capturing nature and relationship of data– Enterprise Data Model–high-level entities and relationships for the

organization– Project Data Model–more detailed view, matching data structure in

database or data warehouse Relational Databases

– Database technology involving tables (relations) representing entities and primary/foreign keys representing relationships

Use of Internet Technology– Networks and telecommunications, distributed databases, client-server,

and 3-tier architectures Database Applications

– Application programs used to perform database activities (create, read, update, and delete) for database users

Page 17: Database Management System

17

Figure 3Figure 1-3 Segment from enterprise data model

Page 18: Database Management System

18

Figure 3Figure 1-3 Segment from enterprise data model

One customer may place many orders, but each order is placed by a single customer

One-to-many relationship

Page 19: Database Management System

19

Figure 3Figure 1-3 Segment from enterprise data model

One order has many order lines; each order line is associated with a single order

One-to-many relationship

Page 20: Database Management System

20

Figure 3Figure 1-3 Segment from enterprise data model

One product can be in many order lines, each order line refers to a single product

One-to-many relationship

Page 21: Database Management System

21

Figure 3Figure 1-3 Segment from enterprise data model

Therefore, one order involves many products and one product is involved in many orders

Many-to-many relationship

Page 22: Database Management System

22

Figure 1-4 Order, Order_Line, Customer, and Product tablesRelationships established in special columns that provide links between tables

Order Order Line Product

Customer

Page 23: Database Management System

23

Figure 1-5 Client/server system for Pine Valley Furniture Company

Page 24: Database Management System

24

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

Page 25: Database Management System

25

The Range ofThe Range ofDatabase ApplicationsDatabase Applications

Page 26: Database Management System

26

Figure 1-7 Typical data from a personal computer database

Page 27: Database Management System

27

Figure 1-8 Workgroup database with local area network

Page 28: Database Management System

28

Enterprise Database ApplicationsEnterprise Database Applications

Enterprise Resource Planning (ERP)– Integrate all enterprise functions

(manufacturing, finance, sales, marketing, inventory, accounting, human resources)

Data Warehouse– Integrated decision support system derived

from various operational databases

Page 29: Database Management System

29

Figure 1-9 An enterprise data warehouse

Page 30: Database Management System

30

Components of the Components of the Database EnvironmentDatabase 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

Page 31: Database Management System

31

Figure 1-10 Components of the database environment

Page 32: Database Management System

32

Evolution of DB SystemsEvolution 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

Page 33: Database Management System

33

Evolution of DB SystemsEvolution of DB Systems

Page 34: Database Management System

34

Memory Database(MemDB) Memory Database(MemDB) TechnologyTechnology

An in-memory database (IMDB; also main memory database system or MMDB) is a database management system that primarily relies on main memory for computer data storage

Main memory databases are faster than disk-optimized databases since the internal optimization algorithms are simpler and execute fewer CPU instructions

In applications where response time is critical, such as telecommunications network equipment main memory databases are often used

Page 35: Database Management System

35

MemDB DurabilityMemDB DurabilityMany MMDBs add durability via the following mechanisms: Transaction Logging, which records changes to the

database in a journal file and facilitates automatic recovery of an in-memory database.

Non-volatile RAM, usually in the form of static RAM backed up with battery power (battery RAM), or an electrically erasable programmable ROM (EEPROM). With this storage, the MMDB system can recover the data store from its last consistent state upon reboot.

High Availability implementations that rely on database replication, with automatic failover to an identical standby database in the event of primary database failure.