Scribd
Upload
13 views18 pages

CHAPTER 3 - Relational Database

Uploaded by

Tan Yong Feng MSUC Penang
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
13 views18 pages

CHAPTER 3 - Relational Database

Uploaded by

Tan Yong Feng MSUC Penang
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 18

ACCOUNTING

INFORMATION SYSTEMS II
Chapter 3: Relational Databases
Learning Objectives
• Explain the importance and advantages of databases,
as well as the difference between database and file-
based legacy systems.
• Explain database systems, including logical and
physical views, schemas, the data dictionary, and
DBMS languages.
• Describe what a relational database is, how it
organizes data, and how to create a set of well-
structured relational database tables.
What Is a Database?
• Efficiently and centrally coordinates information for
a related group of files
• A file is a related group of records
• A record is a related group of fields
• A field is a specific attribute of
interest for the entity (record)
Advantages of Databases
• Data is integrated
• Data sharing
• Minimize data redundancy and inconsistencies
• Data is independent of the programs that use the
data
• Data is easily accessed for reporting and cross-
functional analysis
Database Users and Designers
• Different users of the database information are at
an external level of the database. These users have
logical views of the data.
• At an internal level of the database is the physical
view of the data which is how the data is actually
physically stored in the system.
• Designers of a database need to understand user’s
needs and the conceptual level of the entire
database as well as the physical view.
Schemas
• Conceptual-level—organization wide view
• External-level—individual user’s view
• Internal-level—low level view
Database Design
• To design a database, you need to have a
conceptual view of the entire database. The
conceptual view illustrates the different files and
relationships between the files.
• The data dictionary is a “blueprint” of the
structure of the database and includes data
elements, field types, programs that use the data
element, outputs, and so on.
DBMS Languages
• Data Definition Language (DDL)
• Builds the data dictionary
• Creates the database
• Describes logical views for each user
• Specifies record or field security constraints
• Data Manipulation Language (DML)
• Changes the content in the database
• Creates, updates, insertions, and deletions
• Data Query Language (DQL)
• Enables users to retrieve, sort, and display specific data
from the database
Relational Database
• Represents the conceptual and external schema as
if that “data view” were truly stored in one table.
• Although the conceptual view appears to the user
that this information is in one big table, it really is a
set of tables that relate to one another.
Conceptual View Example
Customer Name Sales Invoice # Invoice Total

D. Ainge 101 $1,447

G. Kite 102 $4,394

D. Ainge 103 $ 898

G. Kite 104 $ 789

F. Roberts 105 $3,994


Relational Data Tables (1 of 2)

Copyright © 2018 Pearson Education, Ltd. Chapter 4: Relational Databases Slide 1 - 11


Relational Data Tables (2 of 2)

Primary Keys
Foreign Key (Customer # is a Foreign key in
the Sales table because it is a Primary key
that uniquely identifies Customers in the
Customer table). Because of this, the Sales
table can relate to the Customer table (see
red arrow above).

Copyright © 2018 Pearson Education, Ltd. Chapter 4: Relational Databases Slide 1 - 12


Why Have a Set of Related Tables?
• Data stored in one large table can be redundant
and inefficient causing the following problems:
• Update anomaly
• Insert anomaly
• Delete anomaly
Relational Database Design Rules

• Every column in a row must be single valued


• Primary key cannot be null (empty) also known as entity integrity
• If a foreign key is not null, it must have a value that corresponds to the
value of a primary key in another table (referential integrity)
• All other attributes in the table must describe characteristics of the object
identified by the primary key
Following these rules allows databases to be normalized and solves the
update, insert, and delete anomalies.
Copyright © 2018 Pearson Education, Ltd. Chapter 4: Relational Databases Slide 1 - 14
Queries
• Users may want specific information found in a
relational database and not have to sort through all
the files to get that information. So they query (ask
a question) the data.
• An example of a query might be: What are the
invoices of customer D. Ainge and who was the
salesperson for those invoices?
Creating the Query

Copyright © 2018 Pearson Education, Ltd. Chapter 4: Relational Databases Slide 1 - 16


Query Answer

Copyright © 2018 Pearson Education, Ltd. Chapter 4: Relational Databases Slide 1 - 17


THE END

Copyright © 2018 Pearson Education, Ltd. Chapter 4: Relational Databases Slide 1 - 18

You might also like