Principles Of Distributed Database Systems Exercise Solutions ((install)) Jun 2026
Are you working on a from the book that you need help with? Principles of Distributed Database Systems, Third Edition
One designated coordinator site manages all lock requests. Problems focus on bottleneck analysis and single-point-of-failure vulnerabilities.
Because a cycle exists, a distributed deadlock is confirmed. Site 2 invokes a resolution policy, selecting a victim transaction (typically based on cost metrics or timestamps) to abort and break the cycle.
Design a distributed query to retrieve all tuples from R1 and R2. Are you working on a from the book that you need help with
:
Designing a distributed database system (DDBS) requires breaking down a global conceptual schema into physical allocations across multiple geographic or logical nodes. The primary mechanisms used to achieve this are horizontal fragmentation, vertical fragmentation, and data allocation. Exercise: Horizontal vs. Vertical Fragmentation
Evaluate the communication cost (total bytes transferred) for two strategies: Ship Whole Relation Semijoin Optimization Solution & Analytical Framework Strategy 1: Ship Whole Relation (S to Site 1) Because a cycle exists, a distributed deadlock is confirmed
No data is lost; every tuple in the global relation must map to at least one fragment.
Concurrency control ensures global schedule serializability across multiple independent sites. Exercise: Distributed 2-Phase Locking (2PL) and Deadlocks Transaction T1cap T sub 1 holds a read lock on item at Site 1 and requests a write lock on item at Site 2. Transaction T2cap T sub 2 holds a read lock on item at Site 2 and requests a write lock on item at Site 1.
Overlapping quorums ensure a read operation always intersects with at least one node containing the latest write. This guarantees strong consistency. : Designing a distributed database system (DDBS) requires
R1:
Define a horizontal fragmentation schema.
Every employee tuple satisfies at least one minterm predicate.
: Solving problems related to 2-Phase Commit (2PC) and distributed deadlock detection.
Consider two relations stored on different network nodes. Node 1: Employee (10,000 tuples, size = 100 bytes/tuple) Node 2: Department (100 tuples, size = 50 bytes/tuple) We need to execute the join query: Employee ⋈DeptID⋈ sub DeptID end-sub