Introduction: Databases and Database Users

Chapter 1
Introduction: Databases andIntroduction: Databases and
Database Users
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

OutlineOutline
Basic DefinitionsBasic Definitions
Typical DBMS Functionality
Example of a Database (UNIVERSITY)Example of a Database (UNIVERSITY)
Main Characteristics of the Database Approach
Database UsersDatabase Users
Advantages of Using the Database Approach
When Not to Use DatabasesWhen Not to Use Databases

Basic DefinitionsBasic Definitions
Data:
Known facts that can be recorded and have an implicit meaning.
Database:
A collection of related data. It has the following implicit properties:
A d t b t t f th l ld tiA database represents some aspect of the real world, sometimes
called the miniworld.
A database is a logically coherent collection of data with some
inherent meaning.
A database is designed, built, and populated with data for specific
purpose.
Examples: Airline reservation system, Students’ registration system
Database Management System (DBMS):Database Management System (DBMS):
A software package/ system to facilitate the creation and maintenance of
a computerized database.
Database System:
y
The DBMS software together with the data itself. Sometimes, the
applications are also included.

Managing DataManaging Data
There are two approaches to manage dataThere are two approaches to manage data
File-based approach: An approach that utilizes a
collection of application programs which performsg
services to end-users (e.g. Reports). Each
program defines and manages its own data.
Database approach: An approach that data is
collected and manipulated using specific softwarecollected and manipulated using specific software
called Database Management System, and many
programs share this data.

File Based ApproachFile-Based Approach
User 1 Application
Dataprograms
Data
User 2
Application
programsprograms

Database ApproachDatabase Approach
User 1 Application
Database
DBMS
programs
User 2 Application
programsprograms

Simplified database system environmentSimplified database system environment

Typical DBMS FunctionalityTypical DBMS Functionality
Define a particular database in terms of its data types,p yp ,
structures, and constraints
Construct or load the initial database contents on a
d t disecondary storage medium
Manipulating the database:
Retrieval: Querying generating reportsRetrieval: Querying, generating reports
Modification: Insertions, deletions and updates to its content
Accessing the database through Web applications
Processing and Sharing by a set of concurrent users and
application programs – yet, keeping all data valid and
consistent
consistent

Typical DBMS FunctionalityTypical DBMS Functionality
Other features:Other features:
Protection or Security measures to prevent
unauthorized access
Maintaining the database and associated programs
over the lifetime of the database application

Example of a Database
(with a Conceptual Data Model)(with a Conceptual Data Model)
Mini-world for the example:Mini world for the example:
Part of a UNIVERSITY environment.
Some mini-world entities:Some mini world entities:
STUDENTs
COURSEsCOURSEs
SECTIONs (of COURSEs)
DEPARTMENTs
INSTRUCTORs

Example of a Database
(with a Conceptual Data Model)(with a Conceptual Data Model)
Some mini-world relationships:p
SECTIONs are of specific COURSEs
STUDENTs take SECTIONs
COURSEs have prerequisite COURSEs
INSTRUCTORs teach SECTIONs
COURSEs are offered by DEPARTMENTsCOURSEs are offered by DEPARTMENTs
STUDENTs major in DEPARTMENTs
Note: The above entities and relationships are typically
expressed in a conceptual data model, such as the
ENTITY-RELATIONSHIP data model (see Chapters 3 4)
ENTITY-RELATIONSHIP data model (see Chapters 3, 4)

Example of a simple databaseExample of a simple database

Main Characteristics of the Database
ApproachApproach
Self-describing nature of a database system:
A DBMS catalog stores the description of a particular
database (e.g. data structures, types, and constraints)
The description is called meta-data.
This allows the DBMS software to work with different
database applications.
Insulation between programs and data:
CCalled program-data independence.
Allows changing data structures and storage organization
without having to change the DBMS access programs.
S t f lti l i f th d tSupport of multiple views of the data:
Each user may see a different view of the database, which
describes only the data of interest to that user.

Main Characteristics of the Database
Approach (continued)Approach (continued)
Sharing of data and multi-user transactiong
processing:
Allowing a set of concurrent users to retrieve from and to
update the databaseupdate the database.
Concurrency control within the DBMS guarantees that each
transaction is correctly executed or aborted
Recovery subsystem ensures each completed transaction
has its effect permanently recorded in the database.
Similarly, each failed transaction is rolled back.y,
OLTP (Online Transaction Processing) is a major part of
database applications. This allows hundreds of concurrent
transactions to execute per second
transactions to execute per second.

Actors on the Scene: They actually use andy y
control the database content; and design,
develop and maintain database applications
D t b Ad i i t tDatabase Administrators
Database Designers
Software EngineersSoftware Engineers
End-users
Workers Behind the SceneWorkers Behind the Scene
Those who design and develop the DBMS
software and related tools.

Actors on the sceneActors on the scene
Database administrators:
Responsible for authorizing access to the database,p g ,
for coordinating and monitoring its use, acquiring
software and hardware resources, controlling its use
and monitoring efficiency of operationsand monitoring efficiency of operations.
Database Designers:
Responsible to define the content the structure theResponsible to define the content, the structure, the
constraints, and functions or transactions against
the database. They must communicate with the
end users and understand their needs
end-users and understand their needs.

Categories of End usersCategories of End-users
Actors on the Scene:
End-users: Are those who require access to the database for
querying, updating, and generating reports. They are categorized
as:
Casual end-users: occasionally access the database, but
they may need different information each time.
Naive or parametric end-users: constantly update and queryNaive or parametric end-users: constantly update and query
databases, using standard types of queries and updates.
Sophisticated end-users: thoroughly familiarize themselves
with the facilities of the DBMS so as to implement theirwith the facilities of the DBMS so as to implement their
application to meet their complex requirements.
Stand-alone end-users: maintain personal databases by
using easy-to-use ready-made program packages
using easy to use ready made program packages.

Advantages of Using the Database
ApproachApproach
Controlling redundancy in data storage and inControlling redundancy in data storage and in
development and maintenance efforts.
Sharing of data among multiple users.g g p
Restricting unauthorized access to data.
Providing persistent storage for program ObjectsProviding persistent storage for program Objects
In Object-oriented DBMSs
Providing Storage Structures (e.g. indexes) forProviding Storage Structures (e.g. indexes) for
efficient Query Processing

Advantages of Using the Database
Approach (continued)Approach (continued)
Providing backup and recovery services.Providing backup and recovery services.
Providing multiple interfaces to different classes
of users.
Representing complex relationships among data.
Enforcing integrity constraints on the databaseEnforcing integrity constraints on the database.
Permitting actions using active rules
triggers stored procedurestriggers, stored procedures

Additional Implications of Using the
Database ApproachDatabase Approach
Potential for enforcing standards:
for data item names, display formats, screens, report
structures, Web page layouts, etc.
Reduced application development time
Flexibility to change data structures:
When requirements change
Availability of current information:y
Extremely important for on-line transaction systems such as
airline, hotel, car reservations.
Economies of scale:
Wasteful overlap of resources and personnel can be
avoided by consolidating data and applications across
departments.

When not to use a DBMSWhen not to use a DBMS
Main inhibitors (costs) of using a DBMS:
Hi h i i i l i d ibl d f ddi i l h dHigh initial investment and possible need for additional hardware.
Overhead for providing generality, security, concurrency control,
recovery, and integrity functions.
When a DBMS may be unnecessary:When a DBMS may be unnecessary:
If the database and applications are simple, well defined, and not
expected to change.
If there are real-time requirements that may not be met because of
DBMS h dDBMS overhead.
If access to data by multiple users is not required
When no DBMS may suffice:
If the database system is not able to handle the complexity of dataIf the database system is not able to handle the complexity of data
because of modeling limitations
If the database users need special operations not supported by
the DBMS.

Introduction: Databases and Database Users

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Introduction: Databases and Database Users (20)

Recently uploaded (20)

Introduction: Databases and Database Users