Download CHAPTER 25 - Distributed Databases and Client*Server Architectures

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Operational transformation wikipedia , lookup

Data Protection Act, 2012 wikipedia , lookup

Expense and cost recovery system (ECRS) wikipedia , lookup

Data model wikipedia , lookup

Data center wikipedia , lookup

Database wikipedia , lookup

Data analysis wikipedia , lookup

Relational model wikipedia , lookup

SAP IQ wikipedia , lookup

Versant Object Database wikipedia , lookup

Clusterpoint wikipedia , lookup

Information privacy law wikipedia , lookup

Data vault modeling wikipedia , lookup

Concurrency control wikipedia , lookup

3D optical data storage wikipedia , lookup

Business intelligence wikipedia , lookup

Database model wikipedia , lookup

Transcript
GROUP MEMBERS
Edwin Acquah
Andria Akua Abraham
Henry Cleland
Francis Asante



Introduction and Concepts
Types of DDBMS
Techniques for DDBMS Implementation





Fragmentation
Replication
Query Processing
Concurrency
Architecture

DDB Technology is a merger between
 Database
Technology
 Networks and Data Communication
Technology
However, developments have been shifted from Pure DDBMS
products to
 Systems based on Client-Server Architectures or
 Developing Technologies for accessing Distributed
Heterogeneous Data sources
 Decentralizing
Of Processing (at the
system level) while achieving an
Integration of Information sources (at
the logical level) within a
geographically distributed systems of
databases, applications and users
 Management
of distributed data
with different levels of transparency
 Increased reliability and availability
 Improved performance
 Easier expansion



Ability to keep track of the data distribution,
fragmentation, and replication by expanding
the DDBMS catalog.
Ability to access remote sites and transmit
queries and data among the various sites via
a communication network.
Executed with the proper management of the
security of the data and the authorization
/access privileges of users.
Degree of homogeneity
Degree of local autonomy



Each server is an independent and
autonomous centralized DBMS.
Used when there is a global view or schema
of the federation of databases that is shared
by the applications.
In heterogeneous FDBS one server may be a
relational DBMS, another a network DBMS
and the third an object or hierarchical DBMS.
 Differences
in data models
 Differences
in constraints
 Differences
in query languages
The universe of discourse from which the
data is drawn
 Representation and meaning
 The understanding, meaning and
subjective interpretation of data
 Transaction and policy constraints
 Derivation of summaries

 Communication
autonomy
 Execution autonomy
 Association autonomy.

Fragmentation




Replication



Vertical Fragmentation (PROJECTION)
Horizontal Fragmentation (SELECT)
Mixed(Hybrid) Fragmentation
Global catalog schema
Degree of replication
Query Processing


Query Decomposition
Semijoins

Issues that arise include:
Dealing with multiple copies of data items
 Failure of individual sites
 Failure of communications links
 Distributed commit
 Distributed DEADLOCK




Based on an extension of centralized locking.
Idea is to designate a particular copy of each
data item as a distinguished copy.
Locks for that data item deal with the
distinguished copy as such all locking and
unlocking requests are sent to the site that
contains that copy.

Primary site technique (Coordinator site)


All distinguished copies are kept on one site.
Risk and impact of failure is high
Primary Site with Backup
-Adds a backup site to curb the high risk of failure.
Primary copy technique
-distribute locks over several sites



Presentation layer
Application layer
Database sever

Distribution transparency