COSC 3380

www.uh.edu/webct
Learn
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

Please find your perfect seat

you will sit there this Semester!

COSC 3380 Database Management

Systems

TAs, please write the seat number on

the class roll,
then create the Master Sitting Chart,
Last Name and First Name under!

From 2:30 to 2:50 PM 20 minutes.

Your UnderGrad TAs, Shannon Furr & Elizabeth Pham & Duy Ta.
Office Hours:
Shannon M&W 11:30 to 12:30
Elizabeth M&W 1:15 to 2:15
Duy T&Th 10 to 11
563 PGH (Computer LAB)

From 2:30 to 2:50 PM 20 minutes.

From 2:30 to 2:50 PM 20 minutes.

From 2:30 to 2:50 PM 20 minutes.

Data quality problems currently

cost U.S. businesses some $600
billion each year!

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

10

From 2:30 to 2:50 PM 20 minutes.

11

From 2:30 to 2:50 PM 20 minutes.

BB Content and Structure.

12

From 2:30 to 2:50 PM 20 minutes.

Please use BB (BlackBoard) email to

communicate with your TA (Teaching
Assistants) and myself.
Process:
1. Email your TA and CC me.
2. TA responds to student and CC me.
13

From 2:30 to 2:50 PM 20 minutes.

Please print and keep with you.

Due first 10 minutes

of the class.

14

From 2:30 to 2:50 PM 20 minutes.

Please print and keep with you.

15

From 2:30 to 2:50 PM 20 minutes.

Please print and keep with you.

16

From 2:30 to 2:50 PM 20 minutes.

Please print and keep with you.

Last day of class
November 30, 2016.

17

From 2:30 to 2:50 PM 20 minutes.

TAs, please start the MASTER sitting chart.

PLEASE enter the Seat Numbers in BB.

18

From 2:50 to 3:45 PM 55 minutes.

19

COSC 3380
Lecture 1

DataBase Management
Systems
(DBMS)
Chapter 1
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

20

Key Terms
Data
Information
Data Model
Schema and Conceptual Schema and Physical
Schema
Transaction
Integrity constraints
Database Management System
Query

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

21

What Is a
Database?
University Systems: A university

wants to store Data about Faculty, Students,

and Courses so that various aspects of this enterprise can be easily
described.

A very large, integrated collection of Data.

Models real-world enterprise.

Entities (e.g., Faculty, Students, Courses)

Relationships (e.g., Madonna is taking CS564)

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

22

What is a Relational
Database?

A Database is like a filling cabinet.

A File is a collection of related

information.

A Record is a collection of information

about a person, place, thing.

A Field is just one component of the

Record and contains one item in the
Database Management Systems 3ed,
record.

R. Ramakrishnan and J. Gehrke

23

What is a Relational
Database?

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

24

What Is a DBMS?
A DataBase Management System (DBMS)
is a software package designed to store and manage
Databases.

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

25

What is a
DBMS?

A DataBase Management System (DBMS)

is a software package designed to store and manage
Databases.

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

26

DBMS tools & Databases

A DBMS gives you the tools to:
Design the structure of your Database.
Create data entry forms so you can get information into the Database.
Validate the Data entered and check for inconsistencies.
Sort and manipulate the Data in the Database.
Query the Database (that is, ask questions about the Data).
Produce flexible reports, both on screen and paper, that make it easy to
comprehend the information stored in the Database.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

27

Put it all together!

DBMS VIDEO LINK

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

28

Several Areas

Database System Implementation. How does one build a

DBMS, including such matters as query processing, transaction
processing and organizing storage for efficient access?

Design of Databases. How does one develop a useful Database?

What kind of information go into the Database? How is the
information structured? How do Data items connect?

Database Programming. How does one express queries and

other operations on the Database? How does one use other
capabilities of a DBMS, such as transactions or constraints, in an
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke
application?

29

Database vs. File Systems

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

30

DBMS vs. Files

Application must move large Datasets between main

memory and secondary storage (e.g., buffering, pageoriented access, 32-bit addressing, etc.)

Special code for different queries

Must protect Data from inconsistency due to multiple

concurrent users

Crash Recovery

Security and Access Control

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

31

Why use a
DBMS?

Data independence and efficient access.

Reduced application development time.

Data integrity and security.

Uniform Data administration.

Concurrent access, Recovery from

crashes.

Data quality problems currently

cost U.S. businesses some $600 billion
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

32

Why study
Databases??

Datasets increasing in diversity and volume.

Digital libraries, Interactive Video, Human Genome

project
... need for DBMS exploding

DBMS encompasses most of CS

OS, Languages, Data Structures, AI, Multimedia, Logic

Database Management Systems

3ed, R. Ramakrishnan and J. Gehrke
http://www.online-stopwatch.com/eggtimer-countdown/full-screen/

33

Data
models
A Data model

is a collection of concepts for describing

Data.

A Schema is a description of a particular collection of

Data, using the a given Data model.

The Relational Data model is the most widely used mode

Main concept: Relation, basically a Table with rows and

columns.

Every Relation has a Schema, which describes the

columns
or fields.
Database Management
Systems 3ed, R. Ramakrishnan and J. Gehrke

34

Levels of
Abstraction
Many Views,

View 1 View 2 View 3

Schema
single Conceptual (Logical) Schema - Conceptual
WHAT
single Physical Schema - HOW.

Physical Schema

Views describe how users see the Data.

Conceptual Schema defines logical structure - WHAT

Schemas
Physical
Schema describes
theusing
FilesDDL;
and Indexes
used
are defined
Data is modified/queried
u
- HOW.

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

35

Example: University
Database

External Schema (View):

Course_Info(cid:string, enrollment:integer)

Conceptual Schema - WHAT:

Student(sid:string, name: string, login: string, age: integ

gpa:real)
Course(cid:string, cname:string, credits:integer)
Enrolled(sid:string, cid:string, grade:string)

Physical Schema - HOW:

Relations

stored as unordered Files (heap).

Index on first column of Student.

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

36

Data
Independence *

WHAT
HOW

Applications insulated from how Data is structured and

stored.

Logical Data independence: Protection from changes in

logical structure of Data - WHAT.

Physical Data independence: Protection from changes in

physical structure of Data - HOW.

One of the most important benefits of using a DBM

37

Database Management
Systems 3ed, R. Ramakrishnan and J. Gehrke

Concurrency
Controlexecution of user programs is essential for
Concurrent

good DBMS performance.

Because disk accesses are frequent, and relatively slow,

it is important to keep the cpu humming by working on
several user programs concurrently.

Interleaving actions of different user programs can

lead to inconsistency: e.g., check is cleared while
account balance is being computed.

DBMS ensures such problems dont arise: users can

pretend they are using a single-user system.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke
38
(ACIDSerializability)

Transactio
n

Key concept is transaction, which is an atomic

sequence of Database actions (reads/writes).

Each transaction, executed completely, must

leave the Database in a consistent state if
Database is consistent when the transaction
begins.
Users can specify some simple integrity constraints on
the Data, and the DBMS will enforce these constraints.
Beyond this, the DBMS does not really understand the
semantics of the Data. (e.g., it does not understand how
the interest on a bank account is computed).
Database
Thus,Management
ensuring
that
a R.transaction(
run alone) preserves39
Systems
3ed,
Ramakrishnan and J. Gehrke

Scheduling Concurrent
DBMS ensures that execution of {T1, ... , Tn} is
Transactions
equivalent to some serial execution T1, ... Tn.

Before reading/writing an object, a transaction requests

a lock on the object, and waits till the DBMS gives it the
lock. All locks are released at the end of the
transaction. (Strict 2PL Locking Protocol.)

Idea: If an action of Ti (say, writing X) affects Tj (which

perhaps reads X), one of them, say Ti, will obtain the lock
on X first and Tj is forced to wait until Ti completes;
this effectively orders the transaction.

What if Tj already has a lock on Y and Ti later requests

a lock on Y? (Deadlock!) Ti or Tj is aborted and restarted!

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

40

Ensuring
Atomicity
DBMS ensures Atomicity (all-or-nothing

property) even if system crashes in the middle of

a Xact.
Idea: Keep a Log (history) of all actions carried out
by the DBMS while executing a set of Xacts:

Before a change is made to the Database, the

corresponding Log entry is forced to a safe location. (WAL
protocol; OS support for this is often inadequate.)

After a crash, the effects of partially executed

transactions are undone using the Log. (Thanks to WAL,
if Log entry wasnt saved before the crash, corresponding

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

41

The
Log

The following actions are recorded in the Log:

Ti writes an object: the old value and the new value.

Log record must go to disk before the changed page!

Ti commits/aborts: a Log record indicating this action.

Log records chained together by Xact id, so its

easy to undo a specific Xact (e.g., to resolve a
Deadlock).

Log is often duplexed and archived on Stable

storage.
All Log related activities (and in fact, all CC related
activities such as lock/unlock, dealing with deadlocks
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke
42
etc.) are handled transparently by the DBMS.

Structure of a
DBMS

A typical DBMS has a

layered architecture.
The figure does not
show the Concurrency
Control and Recovery
components.

These layers
must consider
Concurrency Control and
Recovery

Query Optimization
and Execution
Relational Operators
Files and Access Methods
Buffer Management
Disk Space Management

This is one of several

possible architectures;
each system has its own
variations.

DB

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

43

Databases make these folks

End users
happy
... and DBMS vendors

DB application programmers

e.g. smart webmasters

DataBase Administrator (DBA)

Designs logical /physical Schemas

Handles security and authorization
Data availability, crash recovery
Database tuning as needs evolve

Must understand how a DBMS works!

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

44

The Database System

Environment

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

45

The Database Approach to Data Management

Database:
Collection of related Files containing records on people, places, or things
Prior to digital Databases, business used file cabinets with paper files

Entity
Generalized category representing person, place, thing on which we store
and maintain information
e.g. SUPPLIER, PART

Attributes:
Specific characteristics of each Entity, e.g.:
SUPPLIER name, address
PART description, unit price, supplier

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

46

The Database Approach to Data Management

Relational Database
Organize Data into two-dimensional Tables(Relations) with columns and
rows
One Table/Relation for each Entity

e.g. (CUSTOMER, SUPPLIER, PART, SALES)

Fields (columns) store Data representing an attribute

Rows store Data for separate Data Records/Rows/Tuples/Records
Key field: Uniquely identifies each Record
Primary key:

One or more fields in each Table/Relation

Cannot be duplicated
Provides unique identifier for all information in any Row

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

47

A Relational Database Table/Relation

Table

A Relational Database organizes Data in the form of two-dimensional Tables.

Illustrated here is a Table for the Entity SUPPLIER showing how it represents the
Entity and its attributes. Supplier_Number is the key field.

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

48

The PART Table/Relation

Table

Data for the Entity PART have their own separate Table. Part_Number is the
primary key and Supplier_Number is the foreign key, enabling users to find
related information from the SUPPLIER Table about the Supplier for each Part.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

49

The Database Approach to Data Management

Establishing Relationships
Entity-Relationship Diagram
used to clarify Table Relationships in a Relational Database

Relational Database Tables/Relations may have:

One-to-one Relationship
One-to-many Relationship
Many-to-many Relationship

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

50

The Database Approach to Data Management

A Simple Entity-Relationship
Diagram (ERD) WHAT
Entity-

This Diagram shows the Relationship between the Entities SUPPLIER and PART.

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

51

The Database Approach to Data Management

Normalization
Process of streamlining complex groups of Data to:
Minimize redundant Data elements
Minimize awkward many-to-many Relationships
Increase stability and flexibility

Referential integrity rules

Used by relational Databases to ensure that Relationships between
coupled Tables remain consistent
e.g. When one Table has a foreign key that points to another Table,
you may not add a record to the Table with foreign key (child)
unless there is a corresponding record in the linked Table (parent)

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

52

Sample Order Report

The shaded areas show which Data came from the SUPPLIER, LINE_ITEM, and
ORDER Tables. The Database does not maintain Data on Extended Price or
Order Total because they can be derived from other Data in the Tables.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

53

The Final Database Design with Sample Records

The final design of the Database for Suppliers, Parts, and Orders has four Tables.

The LINE_ITEM Table is a join Table that eliminates the many-to-many Relationship
between ORDER and PART.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

54

Entity-Relationship Diagram (ERD) WHAT for the

Database with Four Tables/Relations
Tables

This Diagram shows the Relationship between the Entities

SUPPLIER, PART, LINE_ITEM, and ORDER.

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

55

DBMS

Examples of DBMS:

DB2, Oracle Database,

Microsoft SQL Server, Microsoft Access, mySQL

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

56

Human Resources Database with Multiple Views

A single human resources Database provides many different Views of Data,

depending on the information requirements of the User. Illustrated here are two
possible Views, one of interest to a benefits specialist and one of interest to a
member of the companys payroll department.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

57

Operations of a Relational DBMS

Select:

Creates a subset of all Records meeting stated criteria

Join:

Combines Relational Tables to present the User with more information

than is available from individual Tables

Project:

Creates a subset of columns in a Table

Permits User to create new Tables containing only desired information

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

58

The Three Basic Operations of a Relational DBMS

The select, project, and join operations enable Data from two different Tables to
be combined and only selected attributes to be displayed.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

59

Capabilities of Database Management Systems

Data Definition capabilities - DDL

Specify structure of content of Database

Data Catalog (Dictionary)

Automated or manual file storing definitions of Data elements and their characteristics

Querying and reporting - DML

Data Manipulation Language
Structured query language (SQL)
Microsoft Access query-building tools - QBE
Report generation, e.g. Crystal Reports

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

60

Access Data Dictionary (Catalog) Features

Microsoft Access has a rudimentary Data dictionary capability that displays

information about the size, format, and other characteristics of each field in a
Database. Displayed here is the information maintained in the SUPPLIER Table.
Database
R. Ramakrishnan andindicates
J. Gehrke that it is a key field. 61
The
smallManagement
key icon toSystems
the left3ed,
of Supplier_Number

Example of an SQL Query

Illustrated here are the SQL statements for a query to select suppliers for parts 137 or 150.

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

62

An Access Query (QBE)

Illustrated here is how the previous query would be constructed using Microsoft
Access query-building tools. It shows the Tables, fields, and selection criteria
used for the query.

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

63

Object-Oriented DBMS (OODBMS)

Stores data and procedures that act on those data as objects
to be retrieved and shared
Better suited for storing graphic objects, drawings, video, than
DMBS designed for structuring data only
Used to manage multimedia components or Java applets in
Web applications
Relatively slow compared to relational DBMS
Object-Relational DBMS: Provide capabilities of both types
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

64

Using Databases to Improve Business Performance

and Decision Making

Databases provide information to help the company run the

business more efficiently, and help managers and employees
make better decisions

Tools for analyzing, accessing vast quantities of data:

Data warehousing
Multidimensional Data Analysis
Data Mining
Utilizing Web interfaces to databases

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

65

Data Warehouses
Data Warehouse
Database that stores current and historical data that may be of interest to
decision makers
Consolidates and standardizes data from many systems, operational and
transactional Databases
Data can be accessed but not altered

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

66

Components of a Data Warehouse

The Data Warehouse extracts current and historical data from multiple
operational systems inside the organization. These Data are combined with Data
from external sources and reorganized into a central Database designed for
management Reporting and Analysis. The information directory provides Users
Database
Management
Systems
Ramakrishnan
and
J. Gehrke
67
with information
about
the 3ed,
DataR.available
in the
Warehouse.

Business Intelligence, Multidimensional Data Analysis,

and Data Mining

Business Intelligence: Tools for Consolidating, Analyzing, and Providing

access to large amounts of Data to improve Decision Making

Software for Database Reporting and Querying

Tools for multidimensional Data Analysis (OnLine Analytical Processing)

Data Mining
e.g. Harrahs Entertainment gathers and analyzes customer data to
create gambling profiles and identify most profitable customers

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

68

Business Intelligence

A series of Analytical Tools works with Data stored in Databases to find patterns
and insights for helping managers and employees make better Decisions to
DatabaseOrganizational
Management Systems
3ed, R. Ramakrishnan and J. Gehrke
69
improve
Performance.

OnLine Analytical Processing (OLAP)

Supports Multidimensional Data Analysis, enabling users to

view the same Data in different ways using multiple
Dimensions

Each aspect of informationproduct, pricing, cost, region, or time period

represents a different dimension
e.g. Comparing sales in East in June vs. May and July

Enables users to obtain online answers to ad hoc questions

such as these in a fairly rapid amount of time

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

70

Multidimensional Data Model

The view that is showing is product versus region. If you rotate the cube 90 degrees,
the face that will show is product versus actual and projected sales. If you rotate the
cube 90 degrees again, you will see region versus actual and projected sales.
Other
views
are possible.
Database
Management
Systems 3ed,

R. Ramakrishnan and J. Gehrke

71

Data Mining

Finds hidden patterns and relationships in large Databases and

infers rules from them to Predict Future Behavior

Types of information obtainable from Data Mining

Associations: Occurrences linked to single event
Sequences: Events linked over time
Classifications: Patterns describing a group an item belongs to
Clusters: Discovering as yet unclassified groupings
Forecasting: Uses series of values to forecast future values

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

72

Data Mining

One popular use of Data Mining: Analyzing patterns in customer data for
one-to-one marketing campaigns or for identifying profitable customers

Predictive analysis:

Uses Data Mining techniques, historical data, and assumptions about

future conditions to predict outcomes of events, such as the probability a
customer will respond to an offer or purchase a specific product

Data Mining vs. Privacy concerns

Used to create detailed Data image about each individual

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

73

Databases and the Web

Firms use the Web to make information from their internal
Databases available to customers and partners

Middleware and other software make this possible

Web server
Application servers or CGI

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

74

Interactive Session Facebook

Database

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

Class Participation!
75

Interactive Session Facebook

Facebook has split its mySQL Database into 4,000 shards in order to
Database?

handle the sites massive data volume, and is running 9,000 instances of
memcached in order to keep up with the number of transactions the
database must serve.
The oft-quoted statistic from 2008 is that the site had 1,800 servers
dedicated to MySQL and 805 servers dedicated to memcached, although
multiple MySQL shards and memcached instances can run on a single
server.
Database Sharding can be simply defined as a "shared-nothing" partitioning scheme for large databases
across a number of servers, enabling new levels of database performance and scalability achievable. If you
think of broken glass, you can get the concept of sharding - breaking your database down into smaller
chunks called shards and spreading those across a number of distributed servers.
The term "sharding" was coined by Google engineers, and popularized through their publication of the Big
Table architecture. However, the concept of "shared-nothing" database partitioning has been around for a
decade or more and there have been many implementations over this period, especially high profile in-house
built solutions by Internet leaders such as eBay, Amazon, Digg, Flickr, Skype, YouTube, Facebook,
Friendster, and Wikipedia.

Class Participation!

http://gigaom.com/cloud/facebook-trapped-in-mysql-fate-worse-than-death/
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke
http://www.codefutures.com/database-sharding/

76

Interactive Session MySpace

Database

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

77

Interactive Session MySpace

Database

http://highscalability.com/myspace-architecture

http://www.communitymx.com/content/article.cfm?cid=A1A63

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

78

Interactive Session: Technology

The Databases Behind MySpace
Read the Interactive Session and then discuss the following
questions:
1. Describe how MySpace uses databases and database servers.
2. Why is database technology so important for a business such as MySpace?
In its initial phases, MySpace opermed with two Web servers communicating with one database server and
3. How effectively does MySpace organize and store the data on its site?
a Microsoft SQL Server database. The site continued adding Web servers to handle increased user requests.
After the number of accounts exceeded 500,000 the site added more SQL Server databases: one served as a
Almost
everything
receives
and serves
to its
users
arerequests.
data objects
audio files
master
database,
theMySpace
others focused
onfrom
retrieving
data
for
user
page
Afterlike
twopictures,
million accounts
4. What
data
management
problems
have
arisen?
How has
MySpace
solved, or
and
files. MySpace
The objects
are very
individualized
and attached
toina which
certainseparate
entity (person).
Itssupported
databases
werevideo
activated,
switched
to
a
vertical
partitioning
model
databases
attempted
to solve,available
these toproblems?
must
theMySpace
objects
anyone
requesting
access
to that
entity.
Database
technology
is the
In
its make
infancy,
used
two Web
communicating
with
one
database
That
was cheaper
adequate
distinct
functions
of thereadily
Web site.
Afterservers
three
million
accounts,
the site
scaled
out server.
by
adding
many
only
technology
that
accomplish
the
mission.
Some
oftothe
problems
MySpace
has
are updating
inadequate
space
on its objects.
databaseObviously
servers, slow
servers
when
the
site
share
had
the
a small
database
number
workload.
of encountered
users
who were
or storage
accessing
database
that
access
or nowith
access
through
its log-in
application,
and users
tooverloads
access
data.
theavailable
years,
wont
work
tens
of
of users.
Unfortunately,
MySpace
more
frequently
than other
It eventually
switched
tomillions
a virtualized
storage
architecture
in inabilities
which still
databases
write
dataOver
to any
MySpace
attempted
fix these
moreonWeb
servers
and
servers. Some
disk, thus
major
Webhas
eliminating
sites.
Withthe
a to
log-in
possibility
errorproblems
of
rateanofapplications
20by
toadding
40 percent
dedicated
some
disk
days,
becoming
the more
site
overloaded.
isdatabase
not effectively
MySpace
were
simplyoradded
without
restructuring
the entire
system
more
efficiently
its hardware
later installed
organizing
storing
a layeron
of
data
servers
at all.between
the database
servers
andtothe
Web
servers touse
store
and serve and
copies
software.
Workloads
distributed
between
serverswouldnt
which caused
of resources.
of frequently
accessedwere
data not
objects
so that evenly
the sites
Web servers
have toinefficient
query theuse
database
MySpace developers continue to redesign the Web sites database, software, and storage systems, to keep pace
servers with lookups as frequently
with its exploding growth, but their job is never done.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

79

Summary

DBMS used to maintain, query large Datasets.

Benefits include Recovery from system Crashes, Concurrent

access, quick application development, Data integrity and
Security.

Levels of abstraction give Data independence.

DBAs hold responsible jobs and are well-paid!

DBMS R&D is one of the broadest, most exciting areas in

CS. Management Systems 3ed, R. Ramakrishnan and J. Gehrke
Database
80

From 2:50 to 3:45 PM 55 minutes.

THE END

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke

81