ITE806D

Computers as Learning Tools

1

Justice Kofi Armah

(PhD)
 TOPIC
Introduction to
Databases
2

2
 Unit Objective(s)
After completing this unit, you should be able to:

Know the potential problems with lists

Understand the reasons for using databases
3
Understand how related tables avoid the problems with lists
Learn the components of a database system
Learn the elements of a database
Learn the purpose of a Database Management System (DBMS)
Understand the functions of a Database application

3
 Database Concepts
A database system is basically a computer
record keeping system.
4
It is a Collection of interrelated data together to
serve multiple application

4
 Purpose of a Database
The purpose of a database is:
 Provides a repository for storing data
 It provides an organized structure (organizational structure)
5 for data
 To provide a mechanism for interacting with data (querying,
creating, modifying, and deleting data CRUD)

A database can store information and relationships that

are more complicated than a simple list
5
 Traditional File System
Before the advent of DBS data was stored in list or
traditional file systems generated by computer.
The advantages of the traditional Filing systems include:
6  Efficiency and
 Simplicity

6
 Problems with Traditional File
System: Redundancy
In a list, each row is intended to stand on its own.
As a result, the same information may be entered
several times
7  For example, a list of courses may include the teachers
name, ID, and phone extension
 If a particular person is currently teaching 5 subjects, his/her
information would appear in the list 5 times

7
 CourseTuter CourseTutorID PhoneNo
Armah 22 0224444444
Arthur-Nyarko 21 0242335526
Armah 23 0224444444
8 Armah 27 0224444444
Nyagorme 26 0330003838
Bervell 18 0787777733
Armah 56 0224444444

8
 List of Project Managers

9
 List Modification
Redundancy and Multiple themes in lists
Create modification problems (Anomalies)
 Deletion problems
10
 Update problems
 Insertion problems

10
 Problems with Traditional File
System: Multiple Themes
In a list, each row may contain information on more
than one theme or business concept.
As a result, certain information might appear in the list
11 only information about other themes or business
concept is also present
 For example, a list of projects may include project manager
information (Name, ID, and Phone Extension) and project
information (ProjectName, ID, StartDate, Budget) in the
same row

11
 List Modification Issues

12

12
 Problems with Traditional File
System: Redundancy Cont’d
Time consuming operation update
Lack of Data Integrity
Lack of Flexibility
13
Poor security

13
 Addressing Information
Complexities
Relational databases are designed to address many of the
information complexity issues that arise in Business

14

14
 Relational Databases
A relational database stores information in tables. Each
information theme (business concept) is stored in its own table
In essence, a relational database will break up a list into several
15
parts.
 One part for each theme in the list
 For example, a Project List might be divided into a CUSTOMER Table,
a PROJECT List might be divided into a CUSTOMER Table, a
PROJECT Table, and a PROJECT_MANAGER Table

15
 A Table
A Table is simply a two dimensional grid of data that contains
columns and rows
In relational database world a column represents different
16
attributes of an Entity and each row of a table represents an
instance of an entity

16
17

17
 Relational Databases Cont’d
A relational database stores information in tables. Each
information theme (business concept) is stored in its own table
In essence, a relational database will break-up a list into
18
several parts
 One part for each theme in the list
 For example, a Project List might b divided into a CUSTOMER Table, a
PROJECT Table, and a Project_Manager Table

18
19

19
 Putting the Pieces Back
Together
In our relational database example, we broke apart our list into
several tables. Somehow the tables must be joined back
together
20
IN a relational database, tables are joined together using
matched pairs of data values
 For example, if a PROJECT has a CUSTOMER, the Customer_ID can
be stored as a column in the Project table. Whenever we need
information about a customer, we can use the Customer_ID to look up
the customer information in the CUSTOMER table

20
21

21
 Sounds like More Work, Not
Less
A relational database is more complicated than a list
However, a relational database minimizes data redundancy,
preserves complex relationships among topics, and allows for
22
partial data (null values)
Furthermore, a relational database provides a solid foundation
for cheating user interface forms and reports

22
 The Structured Query Language
(SQL)
The structured Query Language (SQL) is an international
standard language for creating, processing, and querying
databases and their tables
23
The vast majority of data-driven applications and websites use
SQL to retrieve, format, report, insert, delete, and/or modify
data for users

23
24

24
 SQL Example
We can use SQL to combine the data in the three tables in the
ART Course Database to recreate the original list structure of
the data
 We do this by a SQL SELECT statement.
25

25
26

26
27

27
 Database Systems
The four components of a database system
are:
 Users
28
 Data Application(s)
 Database Management Systems (DBMS)
 Database

28
 Components of a Database
System

29

29
 Users
A user of a database system does not have to be
necessarily human being. Software program can be
users of a database as well. Typically a user:
30  Use a database application to keep track of information
 Use different user interface forms to enter, read, delete, and
query data
 Produce reports

30
 Data Applications
A database applications is a set of one or more computer
software programs or websites that serve as intermediary
between the user and DBMS
31

31
 Database Application
A user interacts with the database application such
admission applications such as students portal, LMS to
access the database by sending queries or requests for
32 data to the DBMS.
A query typically causes some data to be retrieved; a
transaction may cause some data to be read and some
data to be written into the database.

32
 The Database
A Database is a self-directing collections of related
records
Self describing:
33  The database itself contains the definition of its structure
 Metadata are data describing the structure of data in the
database
 Tables within a relational database are related to each other
in some way

33
 Database Content

34

34
 Database Management System
(DBMS)
A DBMS is a collection of programs that manages the database
structure and controls access to the data stored in the
database.
 A DBMS serves as an intermediary between database applications and
35 the database
 The DBMS manages and controls database activities
 The DBMS creates, processes, and administers the databases it
controls
The goal is to provide a means to access and retrieve information
from a database in a convenient and efficient manner

35
 Functions of a DBMS
Creates databases
Create tables
Create supporting structures (relationship within tables)
36
Data storage and retrieval
Read database data (Transaction support)
Authorization services (multiuser access control)
Modify database data (Insert, update, delete)
Maintain database structures

36
 Functions of a DBMS cont’d
Enforce rules
Control concurrency
Data security management
37
Perform data backup and recovery
Data dictionary management
Data transformation and presentation
Data integrity management

37
 Advantages of DBMS
Improved data sharing
Improved data security
Minimized data inconsistency
38
Better data integration
Increased end-user productivity
Improved decision making

38
 Referential Integrity Constraints
A DBMS can enforce many constraints …
Referential integrity constraints ensure that the values of a
column in one table are valid based on the values in another
39
table.
Informally, the referential integrity constraint states that a tuple
in one relation that refers to another relation must refer to an
existing tuple in that relation
 For example, if a 5 was entered as a CustomerID in the PROJECT
table, a Customer having a CustomerID value of 5 must exist in the
CUSTOMER table

39
40

40
 Personal Database Systems
Also called single user database. A single-user database
supports only one user at a time. A single-user database that
runs on a personal computer is called a desktop database.
41
Personal database systems typically:
 Support one application
 Have only a few tables
 Are simple in design
 Involve only one computer
 Support one user at a time

41
 Personal Database Systems

42

42
 Enterprise-Level Database
systems (EDS)
When the database is used by an entire organization and
supports many users (more than 50, usually hundreds) across
many departments, the database is known as an enterprise
database
43
Compared to personal database EDS typically
 spread through many devices
 Support several users simultaneously
 Support more than one application
 Are complex in design
 Have many tables
 Have many databases
43
 Other databases

44

44
45

45