Introduction to Database Management • may have multiple tables

Why Use A Database?

• help people and organizations keep track

of things

• problems of using list to store data :

‑ data inconsistencies
• each row stores data about an occurrence
‑ data privacy
or instance of the interest
• store data in single-theme tables
• stores data and relationships
• tables are related through primary key
and foreign key
Databases Create Information

• data - recorded facts and figures

Hierarchy of A Data
• information - knowledge derived from
data

• databases record data so that we can

produce information

Components of A Database System

DBMS Components

• hardware - physical computer system

• software - program that allows users to

access, maintain and update the data
Characteristics of Databases • data - separate entity from the software
• data is stored in tables which have rows that access them
and columns
• users - (1) end users: people who has ‑ perform backup and recovery
access to the database or (2) application
Examples: Oracle, DB2, Microsoft Access, SQL
program: applications that access and
Server
process data

• procedures - rules that are defined and

followed by the users Database Architecture

Components of A Database System:

Microsoft Access

Application Programs

Functions:

• Create and process forms

• Create and transmit queries

• Create and process reports

• Execute application logic

• Internal Level
• Control application
‑ interact directly with the hardware

Microsoft Access
- a low-end product intended
individual users and small workgroups
- tries to hide much of the underlying
database technology from the user
DBMS : Database Management System
Functions:
‑ create database, tables
supporting structures
‑ read and update database data
• Conceptual Level
‑ define the logical view of the data
for
‑ define the data model
‑ contain the main functions of the
DBMS
‑ intermediary level that free users
from dealing with external level
• External Level
and
‑ interact daily with users
‑ display data in familiar format

‑ maintain database structures

‑ enforce rules

‑ control currency

‑ provide security
Database - self-describing collection of 1. Requirements Phase - a data model is
related records or tables developed

Components: * data model - it is a logical

representation of the database structure
• user data
2. Design Phase - the data model is
• metadata - data about the structure
transformed into tables and relationships
of the database
3. Implementation Phase
• indexes - represent relationships
among the data and also to improve ‑ tables, relationships and
the performance of database constraints are created
applications
‑ stored procedures and triggers
• stored procedures - program are written
modules stored within the database
‑ the database is filled and
• triggers - a procedure that is systems are tested
executed when a particular data
activity occurs
Application Development - parallel with
• application metadata - data
database development
describing application elements such
as forms and reports 1. Requirements Phase

‑ determine app requirements

Types of Databases 2. Design Phase
• personal database - 1 user, < 10 MB ‑ forms, reports, queries and
application code
• workgroup database - < 25 users, < 100
MB 3. Implementation Phase
• organizational database - hundreds to ‑ create forms
thousands users, > 1 trillion bytes
‑ create reports

‑ create queries
Prominent DBMS Products
‑ write application code
• Microsoft Access
‑ test
• Microsoft SQL Server

• IBM DB2
Early Database Models
• Oracle Corporation ORACLE
• before mid-1960s - sequential file
• MySQL processing with magnetic tape

• mid-1960s - disk storage enabled

hierarchical and network database
(3) Phases of Building a Database System
 • internet database

The Relational Model • XML and database integration

• introduced by E.F. Codd in 1970

• DB2 from IBM - first DBMS product

based on the relational model

• other DBMS were developed in late 1980s

• DB2, Oracle & SQL Server - most

prominent commercial DBMS products
on the relational model

Personal Computer DBMS

• the advent of microcomputer increases

popularity of personal databases

• Graphical User Interface (GUI) makes it

easy to use

• Early DBMS products : dBase, R:base &

Paradox

Object-Oriented DBMS (OODBMS)

• object-oriented programming in the

mid-1980s

• goal of OODBMS is to store OOP objects

in the database without having to
transform them into relational format

• Oracle 8i & 9i - allow both relational and

object views of the data on the same
database

Recent History

• success story of the Microsoft Access

‑ Microsoft Office suite and Windows

integration

‑ Easy-to-use and powerful personal

DBMS