Relational Database

Management System

RDBMS-INTRO-SRR 1 12/27/24
 Introduction
2

Purpose of Database Systems

View of Data
Data Models
Data Definition Language
Data Manipulation Language
Transaction Management
Storage Management
Database Administrator
Database Users
Overall System Structure

RDBMS-INTRO-SRR 12/27/24
 Database Management System
(DBMS)
3
Collection of interrelated data and a set of
programs to access the data.
DBMS contains information about a particular
enterprise
DBMS provides an environment that is both
convenient and efficient to use.
Database Applications:
 Banking: transactions
 Airlines: reservations, schedules
 Universities: registration, examination
 Sales: customers, products, purchases
 Manufacturing: production, inventory, orders, supply chain
 Human resources: employee records, salaries, tax deductions
Databases touch all aspects of our lives
RDBMS-INTRO-SRR 12/27/24
 Purpose of Database System
4

In the early days, database applications were

built on top of file systems
Drawbacks of using file systems to store data:
 Data redundancy and inconsistency
 Multiple file formats, duplication of information in
different files
 Difficulty in accessing data
 Need to write a new program to carry out each new task
 Data isolation — multiple files and formats
 Integrity problems
 Integrity constraints (e.g. account balance > 0) become
part of program code
 Hard to add new constraints or change existing ones
RDBMS-INTRO-SRR 12/27/24
 (Cont.)

5
Drawbacks of using file systems (cont.)
 Atomicity of updates
 Failures may leave database in an inconsistent state
with partial updates carried out
 E.g. transfer of funds from one account to another
should either complete or not happen at all
 Concurrent access by multiple users
 Concurrent accessed needed for performance
 Uncontrolled concurrent accesses can lead to
inconsistencies
 E.g. two people reading a balance and updating it
at the same time
 Security problems
Database systems offer solutions to all the
above problems
RDBMS-INTRO-SRR 12/27/24
 Levels of Abstraction
6

Physical level describes how data/a record

(e.g., customer) is stored.

Logical level: describes what data are stored

in database, and the relationships among the
data.

View level: describes what data be accessible

to a specific application/ user.

RDBMS-INTRO-SRR 12/27/24
 View of Data
7

An architecture for a database system

RDBMS-INTRO-SRR 12/27/24
 Instances and Schemas
8

 Schema – the logical structure of the database

 Physical schema: database design at the physical level
 Logical schema: database design at the logical level

 Instance – the actual content of the database at a particular point in

time

 Data Independence: The ability to modify the schema at a level

without requiring to modify the next higher level of abstraction
 Physical Data Independence – the ability to modify the physical
schema without changing the logical schema
 Logical Data Independence – the ability to modify the logical schema
without changing the view schema
 Applications depend on the logical schema
 In general, the interfaces between the various levels and components should
be well defined so that changes in some parts do not seriously influence others.
RDBMS-INTRO-SRR 12/27/24
 Data Models
9
A collection of tools for describing
 data
 data relationships
 data semantics
 data constraints
 Entity-Relationship model
 Relational model
 Other models:
 Object-Oriented model
 Object- Relational data models
 Older models: network model and hierarchical model

RDBMS-INTRO-SRR 12/27/24
 Entity-Relationship Model
10

Example of schema in the entity-relationship model

RDBMS-INTRO-SRR 12/27/24
 Entity Relationship Model (Cont.)
11

E-R model of real world

 Entities (objects)
 E.g. customers, accounts, bank branch
 Relationships between entities
 E.g. Account A-101 is held by customer Johnson
 Relationship set depositor associates customers with
accounts
Widely used for database design
 E-R model is usually converted to the relational

model, which is used for storage and processing

RDBMS-INTRO-SRR 12/27/24
 Relational Model Attributes
12

customer- customer- customer- account-

Customer-id
name street city number

192-83-7465 Johnson
Alma Palo Alto A-101
019-28-3746 Smith
North Rye A-215
192-83-7465 Johnson
Alma Palo Alto A-201
321-12-3123 Jones
Main Harrison A-217
019-28-3746 Smith
North Rye A-201

Example of tabular data in the relational model

RDBMS-INTRO-SRR 12/27/24
 A Sample Relational Database
13

RDBMS-INTRO-SRR 12/27/24
 Data Definition Language (DDL)
14
o Used for specification of the database schema
o E.g.
create table account (
account-number char(10),
balance integer)
o DDL compiler generates a set of tables stored in a data
dictionary
o Data dictionary contains metadata (i.e., data about data)
 database schema

 Data storage and definition language

 language in which the storage structure and access
methods used by the database system are specified
 Usually an extension of the data definition language

RDBMS-INTRO-SRR 12/27/24
 Data Manipulation Language (DML)
15

Language for accessing and manipulating the

data, organized by the appropriate data
model
 DML is also known as query language
Two classes of languages
 Procedural – user specifies what data is required and

how to get those data

 Nonprocedural – user specifies what data is required

without specifying how to get those data

SQL is the most widely used query language

RDBMS-INTRO-SRR 12/27/24
 SQL
16
SQL: widely used non-procedural language
 E.g. find the name of the customer with customer-id 192-83-7465
select customer.customer-name
from customer
where customer.customer-id = ‘192-83-7465’
 E.g. find the balances of all accounts held by the customer with
customer-id 192-83-7465
select account.balance
from depositor, account
where depositor.customer-id = ‘192-83-7465’ and
depositor.account-number = account.account-
number
Application programs generally access databases
through one of
 Language extensions to allow embedded SQL
 Application program interface (e.g. ODBC/JDBC) which allow
SQL queries to be sent to a database
RDBMS-INTRO-SRR 12/27/24
 Database Users
17

Users are differentiated by the way they

expect to interact with the system
 Application programmers – interact with system
through DML calls
 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

 E.g. people accessing database over the web, bank
tellers, clerical staff

RDBMS-INTRO-SRR 12/27/24
 Database Administrator
18

Coordinates all the activities of the

database system; the database
administrator has a good understanding
of the enterprise’s information resources
and needs.
Database administrator's duties include:
 Schema definition
 Storage structure and access method definition
 Schema and physical organization modification
 Granting user authority to access the database
 Specifying integrity constraints
 Acting as liaison with users
 Monitoring performance and responding to
changes in requirements

RDBMS-INTRO-SRR 12/27/24
 Transaction Management
19

A transaction is a collection of operations that

performs a single logical function in a database
application
Transaction-management component ensures
that the database remains in a consistent
(correct) state despite system failures (e.g.,
power failures and operating system crashes)
and transaction failures.
Concurrency-control manager controls the
interaction among the concurrent transactions,
to ensure the consistency of the database.
RDBMS-INTRO-SRR 12/27/24
 Storage Management
20

Storage manager is a program module that

provides an interface between the low-level
data stored in the database and the
application programs and queries submitted
to the system.
The storage manager is responsible to the
following tasks:
 interaction with the file manager
 efficient storing, retrieving and updating of data

RDBMS-INTRO-SRR 12/27/24
 Overall System Structure
21

RDBMS-INTRO-SRR 12/27/24
 Application Architectures
22

Two-tier architecture: E.g. client programs using ODBC/JDBC to

communicate with a database
Three-tier architecture: E.g. web-based applications, and
applications built using “middleware”

RDBMS-INTRO-SRR 12/27/24
 History
23
 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

 Would win the ACM Turing Award for this work

 IBM Research begins System R prototype
 UC Berkeley begins Ingres prototype
 High-performance (for the era) transaction processing

RDBMS-INTRO-SRR 12/27/24
 History
24
 1980s:
Research relational prototypes evolve into commercial
systems
 SQL becomes industrial 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

RDBMS-INTRO-SRR 12/27/24
 Thank you

RDBMS-INTRO-SRR 25 12/27/24