Scribd
Upload
9 views

Lecture-1-Fundamentals-of-Database-systems (1)

The document outlines the fundamentals of database systems, covering topics such as database architecture, data languages, and the history of databases. It discusses the importance of databases in business, the advantages and disadvantages of file-based systems, and various types of metadata. Additionally, it provides a brief history of database development from punched cards to modern relational models and the emergence of NoSQL databases.

Uploaded by

Rio Manuel Valente
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
9 views

Lecture-1-Fundamentals-of-Database-systems (1)

The document outlines the fundamentals of database systems, covering topics such as database architecture, data languages, and the history of databases. It discusses the importance of databases in business, the advantages and disadvantages of file-based systems, and various types of metadata. Additionally, it provides a brief history of database development from punched cards to modern relational models and the emergence of NoSQL databases.

Uploaded by

Rio Manuel Valente
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 51

FUNDAMENTALS OF

DATABASE
SYSTEMS
KENRICK AGUSTIN S. SECUGAL
MASTERS IN NOT MASTERS :D
instructor
hi there! this is not
me…
THIS IS ME :D

I WELCOME MYSELF
TO DBSYS1

皆さん、こんにちは
HELLO EVERYBODY
FUNDAMENTALS 101

• Unit 1: Introduction to Modern Database Systems


• Unit 2: Database Architecture and Date Languages
• Unit 3: Database History
• Unit 4: The Entity-Relationship Model
• Unit 5: The Relational Database Model
• Unit 6: Relational Algebra
• Unit 7: Introduction to Data Normalization
• Unit 8: Introduction to SQL
• Unit 9: Basic Select Statements
• Unit 10: The Join Statement

Saylor Academy.
saylor.org
4
DATABASE IS…

5
LOOK AT THIS
EMPTY BASKET

6
LOOK AT THIS
EMPTY BASKET

7
8
9
10
11
12
BEFORE THE
ADVENT OF
DATABASE
SYSTEMS
Confidence-building strategies
ROLE OF
DATABASES IN
BUSINESS
Everybody uses a database in some way, even if
it is just to store information about their friends
and family. That data might be written down or
stored in a computer by using a word-processing
program or it could be saved in a spreadsheet.
However, the best way to store data is by using
database management software.
This is a powerful software tool that allows you
to store, manipulate and retrieve data in a
variety of different ways.
MEANING OF DATA

Data are factual information such as


measurements or statistics about
objects and concepts. We use data
for discussions or as part of a
calculation.
Data can be a person, a place, an
event, an action or any one of a
number of things. A single fact is an
element of data, or a data
element.

15
DATA CAN BE STORED IN:

• Filing cabinets
• Spreadsheets
• Folders
• Ledgers
• Lists
• Piles of papers on your desk

16
If data are information and
information is what we are in the
business of working with, you can
start to see where you might be
storing it.

All of these items store information, and so too


does a database. Because of the mechanical
nature of databases, they have terrific power
to manage and process the information they
hold. This can make the information they
house much more useful for your work.

17
METADATA
Metadata describes how and when and by
whom a particular set of data was collected,
and how the data is formatted. Metadata is
essential for understanding information stored
in data warehouses and has become
increasingly important in xml-based web
applications.
THERE ARE MANY TYPES OF METADATA.
SOME MAIN CATEGORIES INCLUDE:

• Descriptive: Information that describes a data resource and that is


used for discovery and identification. This may include title, author,
date, keywords, abstract, and video runtime.
• Structural: Information indicating how compound objects are put
together into containers or units. Some examples include how
pages are ordered to form a chapter or how chapters or sections
are structured into the format of a book or DVD.
• Preservation: Provides information that enhances the
maintenance procedures for a digital object or file. Examples
include records of actions taken on the file or the rights attached to
it.
• Administrative: Information that helps manage data, such as
rules, restrictions, and handling instructions.
• Reference: Information on the statistical data related to the file or
object as well as the quality of that data.
• Provenance: Information about the history of data. This is mostly
used for digital data, which are often amended or duplicated. It
records the origin of the digital file and tracks alterations,
duplication, users, methodologies, and other data about events
over the data’s lifecycle.
• Use: Data that is recorded and sorted each time a user accesses or
uses a piece of data. The purpose of this data is to help make
predictions about a user’s future behavior.
• Statistical or process: Describes the processes of collecting,
processing, or producing statistical data.
• Legal: Provides information about the author, rights holder, usage
and licensing, and other legal context of the data.

21
The way in which computers manage data has come a long
way over the last few decades. Today’s users take for granted
the many benefits found in a database system. However, it
wasn’t that long ago that computers relied on a much less
elegant and costly approach to data management called the
file-based system.

22
FILE-BASED SYSTEM

• One way to keep information on a computer is to store it in


permanent files. A company system has a number of
application programs; each of them is designed to
manipulate data files. These application programs have been
written at the request of the users in the organization. New
applications are added to the system as the need arises. The
system just described is called the file-based system.

23
• In a file system, all of the files are organized into directories
and folders, and sometimes the same file can be duplicated
across multiple locations. This means there’s a much greater
chance of data inconsistency with file systems. Plus, file
systems typically have a drastically smaller capacity than a
DBMS and can only modify the metadata of a specific file
rather than its contents

24
ADVANTAGES OF FILE-BASED SYSTEMS

• Easy to use
• Inexpensive
• Faster performance
• Suitable for personal data management

25
DISADVANTAGES OF FILE-BASED
SYSTEMS

• Limited capacity
• Limited functionality
• Less security
• Greater data inconsistency
• No backup or recovery capabilities

26
DATA REDUNDANCY

• Often, within an organization, files and applications are


created by different programmers from various departments
over long periods of time. This can lead to data redundancy,
a situation that occurs in a database when a field needs to be
updated in more than one table. This practice can lead to
several problems such as:
• Inconsistency in data format
• The same information being kept in several different
places (files)

27
• Data inconsistency, a situation where various copies of the
same data are conflicting, wastes storage space and
duplicates effort

28
DATA ISOLATION

• Data isolation is a property that determines when and how


changes made by one operation become visible to other
concurrent users and systems. This issue occurs in a
concurrency situation. This is a problem because:
• It is difficult for new applications to retrieve the
appropriate data, which might be stored in various files.

29
INTEGRITY PROBLEMS

• Problems with data integrity is another disadvantage of using


a file-based system. It refers to the maintenance and
assurance that the data in a database are correct and
consistent. Factors to consider when addressing this issue
are:
• Data values must satisfy certain consistency
constraints that are specified in the application programs.
• It is difficult to make changes to the application
programs in order to enforce new constraints.

30
SECURITY PROBLEMS

Security can be a problem with a file-based approach because:


• There are constraints regarding accessing privileges.

• Application requirements are added to the system


in an
ad-hoc manner so it is difficult to enforce
constraints.

31
EXERCISE
Brain not to damage
• 1. Discuss each of the following terms:

• 1.1 data
• 1.2 field
• 1.3 record
• 1.4 file
• 2. What is data redundancy?
• 3. Discuss the disadvantages of file-based systems.
• 4. Explain the difference between data and information.

33
5. Use figure 1.2 (below) to answer the following questions.
5.1 in the table, how many records does the file contain?
5.2 how many fields are there per record?
5.3 what problem would you encounter if you wanted to produce a listing by city?
5.4 how would you solve this problem by altering the file structure?

34
PART II
35
A BRIEF HISTORY OF DATABASES

Databases are mundane, the


epitome of the everyday in digital
society. Despite the enthusiasm and
curiosity that such a ubiquitous and
important item merits, arguably the
only people to discuss them are
those with curiosity enough to
thumb through the dry and technical
literature that chronicles the
database's ascension.

36
UNIT RECORDS AND PUNCH CARD DATABASES

1880 - Herman Hollerith is the


father of modern machine data
processing. His invention of the
punched card machine marked the
beginning of the automatic data
processing age. Whereas punched
cards had previously been used to
control looms, Hollerith now used
them to store data.

37 Punched card
reader
PUNCH CARD PROLIFERATION

The revolution of data organization


that punch cards instigated soon
translated to domains other than
governance, with companies eager
to gain a competitive edge turning
to this revolutionary means of
restructuring their administration
and services. From 1910 to the mid-
1960s, punch cards and tabulating
mechanisms were the prerequisite
components of any office
environment.

38
FILE SYSTEMS

1960 -The file system was


conceived as an overarching
organizational paradigm
that closely resembled that
of a filing cabinet. Records
were treated as discrete
objects which could be
placed in folders (or
directories). These folders
could themselves be placed
in other folders, creating a
hierarchy that terminated in
a single directory that
contained all records and
child folders.

39
IBM IMS

1960 – First database Hierarchical Data Model


system developed to
Programmer Defined Data Storage
keep track of purchase
orders for Apollo
Mission moon mission

40
41
1970’S COBOL

COBOL (Common Business Oriented


Language)
COBOL was designed for business
computer programs in industries such
as finance and human resources. Unlike
some high-level computer
programming languages, COBOL uses
English words and phrases to make it
easier for ordinary business users to
understand.
Network Data Model schema
Lead by: Charles Bachman

42
43
1970 – RELATIONAL MODEL
CODASYL - Conference/Committee
on Data Systems Language. This
effort led to the development of the
Ted Codd was a mathematician worker
in IBM
programming language COBOL, the
CODASYL Data Model, and other
Designed a mechanism to avoid IMS technical standards.
and CODASYL Programs to be rewritten
every time the database schema or
lay-out changed.
- store database in simple data
structures
-access data through high level
language
- Physical set up

44
1980’S - EARLY RELATIONAL MODEL
- Relational Model Wins
- SEQUEL becomes the standard (SQL)
System R – IBM
- Rise of new DBMS but Oracle wins the
Research
market
INGRES – U. C. - IBM Becomes DB2 in 1983
Berkeley
Oracle – Larry Ellison

Object-oriented Databases
Like XML, JSON

45
46
1990 – BORING DAYS

No major advancements
- Microsoft forks Sybase and creates SQL Server

47
2000 THE BOOM OF THE
INTERNET

Companies have invested in Open Source Database


Companies wrote their own custom middleware to scale out database across
single-node DBMS Instances

Enterprise system used for the analysis and

48
49
2010 – NEW SQL

• Provide performance for OLTP (online


transaction processing) workloads such as
NoSQL DBMS without giving up ACID
(atomic, consistent, isolated, and durable):
- relational
- distributed
- closed-source

50
THANK YOU

You might also like