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

Distributed Database System

This document provides definitions and discusses concepts related to distributed database systems and distributed database management systems. It defines a distributed database as a collection of multiple logically interrelated databases distributed over a computer network. It also defines a distributed database management system as software that manages a distributed database while making the distribution transparent to users.

Uploaded by

Vishnu Lepakshi
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
74 views

Distributed Database System

This document provides definitions and discusses concepts related to distributed database systems and distributed database management systems. It defines a distributed database as a collection of multiple logically interrelated databases distributed over a computer network. It also defines a distributed database management system as software that manages a distributed database while making the distribution transparent to users.

Uploaded by

Vishnu Lepakshi
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 15

DISTRIBUTED

DATABASE SYSTEM

Under the guidance of


Mr. Anisur Rehman

1
DEFINITIONS
Distributed Database – a collection of of
multiple logically interrelated databases
distributed over a computer network
Distributed Database Management
System – A software system that
manages a distributed database while
making he distribution transparent to the
user.

Alimpan Basu CS200119300 2


DEFINITIONS
 It is the software
system that permits Site 1
the management of Site 2
Site 5
the DDBS and makes Communication

the distribution Network

transparent to the
users. Site 4 Site 3

Alimpan Basu CS200119300 3


T0 O M
- autonomous
reliable service
M

T1- db back bone T3/4


- all data replicated
T2 - local db cache
-subset data
O - reliable service
-only local service

O M
Oracle Streams
Cross vendor extract
MySQL Files
Proxy Cache
Alimpan Basu CS200119300 4
Motivations for Distributed DBs
 No centralized point of failure.
 Local Autonomy.
 There’s a whole lot of data out there to store.
 Replication of Data for Disaster Recovery and
High Availability (think RAID on a network)
 High-throughput query processing (either inter-
query or intra-query parallelism), dynamic load-
balancing,

Alimpan Basu CS200119300 5


PROBLEM AREAS
 Directory
Management
Directory
 Distributed DB Design managemen
t

 Concurrency Control Query


Processing
Distributed
DB Design
Reliability

 Deadlock Concurrency
Management Control

 Query Processing Deadlock


Managemen
 Reliability t

Alimpan Basu CS200119300 6


DISTRIBUTED DBMS
ARCHITECTURE

 CLIENT/SERVER
SYSTEMS :
 The simplest is the
case where there is
only one server which
is accessed by
multiple clients.

Alimpan Basu CS200119300 7


Use
r

User Interface External


Handler Schema

Global
Semantic Data
Conceptual
Controller Schema
Interface
Handler
Global Query
Optimizer
Controller
GD/
Interface D
Global
Handler
Execution
Monitor

Local Query Local


Conceptual
Processor Schema

Local Recovery System


Manager Log

Runtime Support Local Internal


Schema
Processor

Alimpan Basu CS200119300 8


DISTRIBUTED DATABASE
DESIGN
 TOP-DOWN DESIGN PROCESS :The
activity begins with a requirement analysis
that defines the environment of the system
and “elicits both the data and processing
needs of all potential database users”.
 There is a relationship between the
conceptual design and the view design.

Alimpan Basu CS200119300 9


DISTRIBUTED DATABASE
DESIGN
 BOTTOM-UP DESIGN PROCESS : A
number of database already exist, and the
design task involves integrating them into
one data base

Alimpan Basu CS200119300 10


FRAGMENTATION
 Why fragment at all?
 How should we fragment?
 How much should we fragment?
 How should we allocate?
 What is the necessary information for
fragmentation and allocation?

Alimpan Basu CS200119300 11


FRAGMENTATION TYPES
 HORIZONTAL FRAGMENTATION :There are
two versions of horizontal partitioning, primary
and derived.
 Store Whole Tuples on Different machines. Nice
because we can use standard relational algebra
statements to define a restriction on a relation
that creates these:
”newyork” (City)
 “chicago” (City)

Alimpan Basu CS200119300 12


FRAGMENTATION TYPES
 VERTICAL FRAGMENTATION : Vertical
fragmentation has been investigated within the
context of centralized database systems as well
as distributed ones.
 Store Different Fields of the same tuples on
Different machines.
Use Projection Op to declare these:
 (Acct #, Branch, Client Name Account)
 (Acct #, Balance Account)
Alimpan Basu CS200119300 13
DRAWBACKS OF DDBs:
 Security
 Increased complexity of Database Design
 Increased complexity of Software
 Data integrity and resolution of concurrent
operations.
 Cost

Alimpan Basu CS200119300 14


Alimpan Basu CS200119300 15

You might also like