E-Module in

Database
Management
System 1
2015 Revised Edition
By: Dr. Melani L. Castillo
 Module 1:
Introduction to Database
& Database System
 What is a Database?
• A database is a collection of related data. By data, we
mean known facts that can be recorded and that have
implicit meaning.
• A very large, integrated collection of non-redundant data
which can be shared by different application systems
• A database is a logically coherent collection of data with
some inherent meaning.
• A database is designed, built, and populated with data for
a specific purpose.It has an intended group of users and
some preconceived applications in which these users are
interested.
 ?
Why Study Databases??
• Shift from computation to information
– at the “low end”: scramble to webspace (a
mess!)
– at the “high end”: scientific applications
• Datasets increasing in diversity and
volume.
– Digital libraries, interactive video, application
systems... need for DBMS exploding
• DBMS encompasses most of CS
– OS, languages, theory, “AI”, multimedia, logic

Watch : What is a Database video?

 Database Applications
• Banking: all transactions
• Airlines: reservations, schedules
• Universities: registration, grades
• Sales: customers, products, purchases
• Online retailers: order tracking, customized
recommendations
• Manufacturing: production, inventory, orders, supply
chain
• Human resources: employee records, salaries, tax
deductions
• E-commerce

Therefore…databases touch all aspects of our lives

 What is a DBMS?
• A Database Management System (DBMS) is a
software package designed to store and manage
databases..
• The DBMS is a general-purpose software system that
facilitates the processes of defining, constructing,
manipulating, and sharing databases among various
users and applications.
• Set of programs to access the data
• An environment that is both convenient and
efficient to use
 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
Database Management System (DBMS)
 Why Use a DBMS?
• Data independence and efficient access.
• Reduced application development time.
• Data integrity and security.
• Uniform data administration.
• Concurrent access, Resiliency: recovery from crashes.
• Persistent storage management
• High level query and data manipulation language
• Efficient query processing
• Transaction management
• Interface with programming languages
Simplified database system environment
 History of Database Systems
• 1950s and early 1960s:
– Data processing using magnetic tapes for storage
• Tapes provide only sequential access
– Punched cards for input
• Late 1960s and 1970s:
– Hard disks allow direct access to data
– Network and hierarchical data models in widespread use
– Ted Codd defines the relational data model
• win the ACM Turing Award for this work
– Relational Model based Systems:
• Relational model was originally introduced in 1970, was heavily researched and
experimented within IBM Research and several universities.
• Relational DBMS Products emerged in the early 1980s.
– High-performance (for the era) transaction processing
 History (cont.)
• 1980s:
– Research relational prototypes evolve into commercial systems
• SQL becomes industry standard
– Parallel and distributed database systems
– Object-oriented database systems
• 1990s:
– Large decision support and data-mining applications
– Large multi-terabyte data warehouses
– Emergence of Web commerce
• 2000s:
– XML and XQuery standards
– Automated database administration
– Increasing use of highly parallel database systems
– Web-scale distributed data storage systems
 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 medium
• 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 – yet, keeping all data valid and
consistent
DBMS Functionality cont…

– Protection or Security measures to 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
 Levels of Abstraction

External Schema1 External Schema 2

•Physical schema: files, indexes

Conceptual Schema hash tables.
•Conceptual schema: tables and
their attributes
Physical Schema •External schema: views of the
different applications, classes of
users.
Disk
 Components of DBMS

• Data Definition Languages (DDL) to define

conceptual, logical and external models
• Data manipulation and query language
called Structured Query Language (SQL)
• Features to implement security
• Checkpointing and roll back recovery
procedures
• Record of accesses.
• Audit trail of changes
 These layers
Structure of a DBMS must consider
concurrency
control and
recovery

• A typical DBMS has a Query Optimization

layered architecture. and Execution
• This is one of several Relational Operators
possible architectures;
each system has its own Files and Access Methods
variations. Buffer Management

Disk Space Management

DB
Overall System Structure
 Database Architecture
The architecture of a database systems is
greatly influenced by the underlying
computer system on which the database is
running:
• Centralized
• Client-server
• Parallel (multiple processors and disks)
• Distributed
Database Application Architectures

(web browser)

Old Modern
Example of Simple Database
 Database Users
Users are differentiated by the way they expect to interact with
the system
– 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.
 Database Users
• Application programmers – interact with system
through DML calls
• Sophisticated users – form requests in a database
query language
• Specialized users – write specialized database
applications that do not fit into the traditional data
processing framework
• Naïve users – invoke one of the permanent
application programs that have been written
previously
– Examples, people accessing database over the
web, bank tellers, clerical staff
 Database Administrator
• Coordinates all the activities of the database system
– has a good understanding of the enterprise’s
information resources and needs.
• Database administrator's duties include:
– Storage structure and access method definition
– Schema and physical organization modification
– Granting users authority to access the database
– Backing up data
– Monitoring performance and responding to
changes
• Database tuning
Steps in Designing Database
 CHARACTERSTICS OF A GOOD
DATA BASE DESIGN
• Satisfy current and future needs of organization
• Cater to unanticipated user requirements in the
best possible way
• Expandable with growth and changes in
organization
• Easy to change when hardware and software
change
• Ensure data security by allowing only authorized
persons to access and modify database
More About Database?

Please watch the Video….

 End of Module 1

What’s Next…..

Tipster says, “Don’t hesitate to ask

questions. Knowledge is just a query
away!”
 Q&A
1. Give an example of a database in a real world
application.
2. Discuss one functionality of a database and explain
where it can be applied.
3. Differentiate the three levels of abstraction in a
database?
4. Why it is necessary to follow the steps in designing a
database?
5. Explain the requirements to have a good design for a
data base?
6. After learning database management system, what role
of a database user would you like to be in the future?
 References
1. Raghu Ramakrishnan, Database
Management Systems, McGraw Hill, 3rd
edition, 2003 (text book).
2. R. Elmasri, S.B. Navathe, Fundamentals of
Database Systems, 6th edition, Addison-
Wesley, 2004.
3. A. Silberschatz, H.F. Korth, S. Sudarshan,
Database System Concepts, McGraw Hill, 4th
edition, 2002.