Unit 1

Distributed DBMS
A distributed database management system is a software system that

permits the management of a distributed database and makes the
distribution transparent to the users.
A distributed database is a collection of multiple, logically
interrelated databases distributed over a computer network.
 Collections of data (eg. in a database) can be distributed across multiple
physical locations.
 A distributed database is distributed into separate partitions/fragments.
 Each partition/fragment of a distributed database may be replicated.

Distributed Processing
Distributed Data Processing is the operations that occurs when an

application distributes its tasks among different computers in a network.
A database application typically distributes front-end presentation tasks

to client computers and allows a back-end database server to manage
shared access to a database. Consequently, a distributed database
application processing system is more commonly referred to as a
client/server database application system.
Distributed database systems employ a distributed processing

architecture. For example, an Oracle Database server acts as a client
when it requests data that another Oracle Database server manages.
Distributed Vs Centralized Database
1. A centralized database keeps its data in storage devices that are in a

single location connected to a single CPU, a distributed database
system keeps its data in storage devices that are possibly located in
different geographical locations and managed using a central DBMS.
2. A centralized database is easier to maintain and keep updated since

all the data are stored in a single location.
But keeping the data up to date in distributed database system
requires additional work, therefore increases the cost of maintenance
and complexity and also requires additional software for this purpose.
Distributed Vs Centralized Database contd…
3. Furthermore, it is easier to maintain data integrity and avoid the

requirement for data duplication. But, all the requests coming to
access data are processed by a single entity such as a single
mainframe, and therefore it could easily become a bottleneck.
But with distributed databases, this bottleneck can be avoided since
the databases are parallelized making the load balanced between
several servers.
4. Furthermore, designing databases for a distributed database is more

complex than the same for a centralized database.
Transparency in a Distributed Database System
1. Location Transparency
2. Replication Transparency
3. Failure Transparency
4. Concurrency Transparency
1.Location Transparency
Although data are geographically distributed and may move from
place to place, with location transparency, users (including
developers) can act as if all the data were located at a single node
SELECT * FROM Customer@sales WHERE TotalSales < 100,000;
Notice that this SQL request does not require the user to know where the data
are physically stored. The distributed DBMS at the local site (San Mateo) will consult
and determine that this request must be routed to New York .
2.Replication Transparency
Although the same data item may be replicated at several nodes in a network, with
replication transparency (sometimes called fragmentation transparency), the developer
(or other user) may treat the item as if it were a single item at a single node. An
identical copy of this file is maintained at all three nodes (full replication). First,
consider the problem of reading part (or all) of this file at any node. The distributed
DBMS will consult the data directory and determine that this is a local transaction (i.e.,
it can be completed using data at the local site only). Thus, the user need not be aware
that the same data are stored at other sites.
3.Failure Transparency
The distributed DBMS is responsible for database recovery when a failure has
occurred. The distributed DBMS at each site has a component called the transaction
manager that performs two functions:
1. Maintains a log of transactions and before and after database images
2. Maintains an appropriate concurrency control scheme to ensure data integrity
during parallel execution of transactions at that site.
4.Concurrency Transparency
The problem of concurrency control is more complex in a distributed
database, because the multiple users are spread out among multiple
sites and the data are often replicated at several sites, as well.
The objective of concurrency management is easy to define but often
difficult to implement in practice. Although the distributed system runs
many transactions concurrently, concurrency transparency allows
each transaction to appear as if it were the only activity in the
system.
Advantages of DDBMS…
1. Data sharing and Distributed Control:
2. Reliability and Availability
3. Speed up Query Processing

THANK YOU

Unit 1

Uploaded by

Copyright:

Available Formats

Unit 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unit 1

Uploaded by

Copyright:

Available Formats

Distributed DBMS

A distributed database management system is a software system that

 A distributed database is distributed into separate partitions/fragments.

 Each partition/fragment of a distributed database may be replicated.

Distributed Data Processing is the operations that occurs when an

A database application typically distributes front-end presentation tasks

Distributed database systems employ a distributed processing

1. A centralized database keeps its data in storage devices that are in a

2. A centralized database is easier to maintain and keep updated since

3. Furthermore, it is easier to maintain data integrity and avoid the

4. Furthermore, designing databases for a distributed database is more

SELECT * FROM Customer@sales WHERE TotalSales < 100,000;

1. Data sharing and Distributed Control:

2. Reliability and Availability

3. Speed up Query Processing

You might also like