0% found this document useful (0 votes)
236 views

Introduction: Databases and Database Users

This document provides an introduction and overview of databases and database management systems (DBMS). It defines key terms like database, data, and DBMS. It describes typical DBMS functionality including defining and loading data, data retrieval and modification, and concurrency control. It also provides an example database for a university and discusses the main characteristics and advantages of the database approach.

Uploaded by

Ehmaid Saber
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
236 views

Introduction: Databases and Database Users

This document provides an introduction and overview of databases and database management systems (DBMS). It defines key terms like database, data, and DBMS. It describes typical DBMS functionality including defining and loading data, data retrieval and modification, and concurrency control. It also provides an example database for a university and discusses the main characteristics and advantages of the database approach.

Uploaded by

Ehmaid Saber
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 25

Introduction: Databases and Database Users

Outline
Types of Databases and Database Applications
Basic Definitions
Typical DBMS Functionality
Example of a Database (UNIVERSITY)
Main Characteristics of the Database Approach
Database Users
Advantages of Using the Database Approach
When Not to Use Databases

Slide 1- 2
Types of Databases and Database
Applications
Traditional Applications:
 Numeric and Textual Databases
More Recent Applications:
 Multimedia Databases
 Geographic Information Systems (GIS)
 Data Warehouses
 Real-time and Active Databases
 Many other applications
First part of book focuses on traditional applications
A number of recent applications are described later in the
book (for example, Chapters 20,21,22,23,24, 25 and 30)

Slide 1- 3
Basic Definitions
 Database:
 A collection of related data.
 Data:
 Known facts that can be recorded and have an implicit meaning.
 Database Management System (DBMS):
 A software package/ system to facilitate the creation and
maintenance of a computerized database.
 Database System:
 The DBMS software together with the data itself. Sometimes, the
applications are also included.

Slide 1- 4
Simplified database system environment

Slide 1- 5
Typical DBMS Functionality
Define a particular database in terms of its data types,
structures, and constraints
Construct or Load the initial database contents on a
secondary storage
Manipulating the database:
 Retrieval: 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, keeping all data valid and consistent

Slide 1- 6
Typical DBMS Functionality
Other features:
Protection or Security :prevent unauthorized access
“Active” processing to take internal actions on data
Presentation and Visualization of data
Maintaining the database and associated programs over
the lifetime of the database application
 Called database, software, and system maintenance

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

Slide 1- 8
Example of a Database
(with a Conceptual Data Model)
Some mini-world relationships:
 SECTIONs are of specific COURSEs
 STUDENTs take SECTIONs
 COURSEs have prerequisite COURSEs
 INSTRUCTORs teach SECTIONs
 COURSEs 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)

Slide 1- 9
Example of a simple database

Slide 1- 10
Main Characteristics of the
Database Approach
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:
 Called program-data independence.
 Allows changing data structures and storage organization
without having to change the DBMS access programs.

Slide 1- 11
Example of a simplified database catalog

Slide 1- 12
Main Characteristics of the
Database Approach (continued)
Data Abstraction:
A data model is used to hide storage details and
present the users with a conceptual view of the
database.
Programs refer to the data model constructs rather
than data storage details
Support 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.

Slide 1- 13
Main Characteristics of the
Database Approach (continued)
Sharing of data and multi-user transaction
processing:
 Allowing a set of concurrent users to retrieve from and to
update 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
 OLTP (Online Transaction Processing) is a major part of
database applications. This allows hundreds of concurrent
transactions to execute per second.

Slide 1- 14
Database Users
Users may be divided into
Those who actually use and control the database
content, and those who design, develop and maintain
database applications (called “Actors on the Scene”),
and
Those who design and develop the DBMS software and
related tools, and the computer systems operators
(called “Workers Behind the Scene”).

Slide 1- 15
Database Users
Actors on the scene
Database administrators:
 Responsible for authorizing access to the database, for
coordinating and monitoring its use, acquiring software and
hardware resources, controlling its use and monitoring
efficiency of operations.
Database Designers:
 Responsible 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.

Slide 1- 16
Categories of End-users
Actors on the scene (continued)
End-users: They use the data for queries, reports and
some of them update the database content.

Slide 1- 17
Advantages of Using the Database
Approach
Controlling redundancy in data storage and in
development and maintenance efforts.
Sharing of data among multiple users.
Restricting unauthorized access to data.
Providing persistent storage for program Objects
In Object-oriented DBMSs – see Chapters 20-22
Providing Storage Structures (e.g. indexes) for
efficient Query Processing

Slide 1- 18
Advantages of Using the Database
Approach (continued)
Providing backup and recovery services.
Providing multiple interfaces to different classes of
users.
Representing complex relationships among data.
Enforcing integrity constraints on the database.
Drawing inferences and actions from the stored data
using deductive and active rules

Slide 1- 19
Additional Implications of Using
the Database Approach
Potential for enforcing standards:
This is very crucial for the success of database
applications in large organizations. Standards refer to
data item names, display formats, screens, report
structures, meta-data (description of data), Web page
layouts, etc.
Reduced application development time:
Incremental time to add each new application is
reduced.

Slide 1- 20
Additional Implications of Using the
Database Approach (continued)
Flexibility to change data structures:
Database structure may evolve as new requirements are
defined.
Availability of current information:
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.

Slide 1- 21
Extending Database
Capabilities
 New functionality is being added to DBMSs in the following areas:
 Scientific Applications
 XML (eXtensible Markup Language)
 Image Storage and Management
 Audio and Video Data Management
 Data Warehousing and Data Mining
 Spatial Data Management (GIS)
 Time Series and Historical Data Management

 The above gives rise to new research and development in incorporating


new data types, complex data structures, new operations and storage
and indexing schemes in database systems.

Slide 1- 22
When not to use a DBMS
Main inhibitors (costs) of using a DBMS:
 High 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:
 If the database and applications are simple, well defined, and
not expected to change.
 If there are stringent real-time requirements that may not be
met because of DBMS overhead.
 If access to data by multiple users is not required.

Slide 1- 23
When not to use a DBMS
When no DBMS may suffice:
If 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.

Slide 1- 24
Summary
Types of Databases and Database Applications
Basic Definitions
Typical DBMS Functionality
Example of a Database (UNIVERSITY)
Main Characteristics of the Database Approach
Database Users
Advantages of Using the Database Approach
When Not to Use Databases

Slide 1- 25

You might also like