Scribd
Upload
45 views

1.0 Introduction (Part1)

The document provides an introduction to database systems. It differentiates between data and information, explaining that data are raw facts while information is produced by processing data. It also differentiates between file-based systems and database systems, noting that file-based systems have limitations like data duplication and lack of data sharing, while database systems address these issues through logical data relationships and centralized data storage and management. The document introduces the three-level ANSI-SPARC architecture for database systems and the concept of data independence it provides.

Uploaded by

Heap Ke Xin
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
45 views

1.0 Introduction (Part1)

The document provides an introduction to database systems. It differentiates between data and information, explaining that data are raw facts while information is produced by processing data. It also differentiates between file-based systems and database systems, noting that file-based systems have limitations like data duplication and lack of data sharing, while database systems address these issues through logical data relationships and centralized data storage and management. The document introduces the three-level ANSI-SPARC architecture for database systems and the concept of data independence it provides.

Uploaded by

Heap Ke Xin
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 40

CHAPTER 1

INTRODUCTION TO
DATABASE
(PART 1)
Objectives
2

At the end of this sub-chapter, students should be able to:

 Differentiate data and information


 Differentiate file processing and database system
 Explain database structure and the three-level
architecture
 Explain the evolution of database and the database
system environment
DATA VS INFORMATION
3

1) STID3013 – A
2) CGPA – 3.42
3) Height – 1.70 m
4) Name – Jack
5) Average Marks for STID3013 – 70.5
6) 24/8/2010 - The date of your mid sem
exam.
Differences between Data and
Information
4

 Data are raw facts, i.e. telephone number, birth


date, name, etc.
 Data : building blocks of information
 Information is produced by processing data
 Information is used to reveal the meaning of data
Data vs. Information
5

SIRIUS SATELLITE RADIO INC.

Data
 6.34
 6.45 Stock Price
 6.39
 6.62
 6.57
 6.64
 6.71
 6.82
 7.12
Last 10 Days
 7.06
DATA vs INFO - Conclusion
6
Examples of Database Applications
7

 Purchases from the supermarket


 Purchases using your credit card
 Booking a holiday at the travel agents
 Using the local library
 Taking out insurance
 Using the Internet
 Studying at university
Database
8

 Shared collection of logically related data (and


a description of this data), designed to meet
the information needs of an organization.
 Logically related data comprises entities,
attributes, and relationships of an
organization's information.
 Description of data known as System catalog
(metadata or data dictionary) provides
program–data independence.
Logically Related Data
9

 Entity – a distinct object in the organization, i.e. a


person, place, thing, concept, or event.
 Attribute – a property that describes some aspect of
entity.
 Relationship – an association between entities
File-based Systems
10

 Collection of application programs that perform


services for the end users (e.g. reports).
 Each program defines and manages its own
data.
File-based Processing
11
Limitations of File-based Approach
12

 Separation and isolation of data


 Each program maintains its own set of data.
 Users of one program may be unaware of
potentially useful data held by other programs.

 Duplication of data
 Same data is held by different programs.
 Wasted space and potentially different values
and/or different formats for the same item.
Limitations of File-based Approach
13

 Data dependence
 File structure is defined in the program code.

 Incompatible file formats


 Programs are written in different languages, and so
cannot easily access each others files.

 Fixed Queries/Proliferation of application programs


 Programs are written to satisfy particular functions. Any
new requirement needs a new program.
Limitations of File-based Approach
14

 Definition of data was embedded in application


programs, rather than being stored separately and
independently.

 No control over access and manipulation of data


beyond that imposed by application programs.
ANSI-SPARC Three-level Architecture
15
ANSI-SPARC Three-level Architecture
16

 External Level
 Users' view of the database.
 Describes that part of database that is relevant to a
particular user.
 Conceptual Level
 Community view of the database.
 Describes what data is stored in database and
relationships among the data.
 Internal Level
 Physical representation of the database on the
computer.
 Describes how the data is stored in the database.
Differences between Three Levels of ANSI-SPARC
Architecture
17
Objectives of Three-Level Architecture
18

 All users should be able to access same data.

 A user's view is immune to changes made in other


views.

 Users should not need to know physical database


storage details.
Objectives of Three-Level Architecture
19

 DBA should be able to change database storage


structures without affecting the users' views.

 Internal structure of database should be unaffected by


changes to physical aspects of storage.

 DBA should be able to change conceptual structure of


database without affecting all users.
Major objective of Three-Level Architecture:Data
Independence
20

 means: the upper levels are unaffected by


changes to lower levels

1. Logical Data Independence


2. Physical Data Independence
Data Independence
21

 Logical Data Independence


 Refers to immunity of external schemas to changes in conceptual
schema.
 Conceptual schema changes (e.g. addition/removal of entities).

 Should not require changes to external schema or rewrites of


application programs.
Data Independence
22

 Physical Data Independence


 Refers to immunity of conceptual schema to changes in
the internal schema.
 Internal schema changes (e.g. using different file
organizations, storage structures/devices).
 Should not require change to conceptual or external
schemas.
Data Independence and the ANSI-SPARC Three-
level Architecture
23
Evolution of Database Systems
24

 First-generation
 Hierarchical and Network
 disadvantages: - complex programs
- minimal data independence
- no accepted theoretical foundation
 Second generation
 Relational
 problems: limited modeling capabilities
 Third generation
 Object Relational
 Object-Oriented
The Database System Environment
25
The Database System Environment
26

 Hardware
 Can range from a PC to a network of computers.

 Software
 DBMS, operating system, network software (if necessary) and also
the application programs.

 Data
 Used by the organization and consists of operational data and the
meta-data.
The Database System Environment
27

 Procedures
 Instructions and rules that should be applied to the
design and use of the DBMS.

 People (Roles in DBMS Environment)


 Data Administrator (DA)
 Database Administrator (DBA)
 Database Designers (Logical and Physical)
 Application Programmers
 End Users (naive and sophisticated)
The Database System Environment

Database Systems: Design,


Implementation, & Management,
6th Edition, Rob28
& Coronel
Database Management System (DBMS)
29

 A software system that enables users to define,


create, and maintain the database and which
provides controlled access to this database.
Database Management System (DBMS)
30

The DBMS Manages the Interaction Between the End User


and the Database
DBMS Facilities
31

 Data definition language (DDL)


 Permits specification of data types, structures and
any data constraints.
 All specifications are stored in the database.

 Data manipulation language (DML)


 General enquiry facility (query language) of the
data.
DBMS Facilities
32

 Controlled access to database may include:


 A security system – prevents unauthorized users accessing the
d/b.
 An integrity system – maintains the consistency of stored data.
 A concurrency control system – allows shared access of the
d/b.
 A recovery control system – restores the d/b to a previous
consistent state following a hardware or software failure.
 A user-accessible catalog – contains descriptions of the data in
the d/b.
DBMS Facilities
33

 A view mechanism.
 Provides users with only the data they want or need to use.
Views
34

 Allows each user to have his or her own view of


the database.

 A view is essentially some subset of the


database.
Views
35

 Benefits include:
 Reduce complexity;
 Provide a level of security;

 Provide a mechanism to customize the appearance


of the database;
 Present a consistent, unchanging picture of the
structure of the database, even if the underlying
database is changed.
Advantages of DBMS
36

 Control of data redundancy


 File-based systems waste space by storing same info in more than one file

 Data consistency
 Reduced the risk by eliminating/controlling Data Redundancy – update once

 More information from the same amount of data.


 Possible to derive additional information from the same data

 Sharing of data
 Authorized user can share the same data

 Improved data integrity


 Validity, rules enforcement  integrity  constraint
Advantages of DBMS (continue...)
37

 Improved security
 Protection from unauthorized user
 Enforcement of standards
 Allow DBA to define and the DBMS to enforce necessary standards
 Economy of scale
 Cost saving
 Balanced conflicting requirements
 Each user has needs that may be conflict with the needs of other users – DBA can design database
that provide best use of resources for the organization as a whole
 Improved data accessibility and responsiveness
 Through query – list certain data
Advantages of DBMS (continue...)
38

 Increased productivity
 DBMSs provide standard functions that programmer have to write on their own

 Improved maintenance through data


independence
 DBMS separates the data descriptions from the application, thereby making
applications immune to changes in data descriptions

 Increased concurrency
 Two or more users allowed to access the same file/data simultaneously

 Improved backup and recovery services


 DBMSs provide facilities to minimize the amount of processing that is lost/failure.
Disadvantages of DBMS
39

 Complexity
 Functionality  makes DBMSs complex – must understand the functionalities to
make full use of DBMS

 Size
 Requiring substantial amounts of memory to run efficiently

 Cost of DBMS
 License/memberships/single;multiple users/maintenance

 Additional hardware costs


 Storage space etc
Disadvantages of DBMS (continue..)
40

 Cost of conversion
 Converting existing applications to run the new DBMS & hardware

 Performance
 Many applications/high load/peak time

 Higher impact of a failure


 Failure of certain components can bring operations to a halt

You might also like