Advanced Database Management System
Advanced Database Management System
Name: Keyur Shah Roll No: 135 MBA Tech (IT) Div B
Component Role
Sites in Distributed DBMS can work independently to handle local transactions or work together to handle global transactions. Nodes in Parallel DBMS can only work together to handle global transactions.
Design Purposes
Distributed DBMS is for: Sharing Data, Local Autonomy, High Availability Parallel DBMS is for: High Performance, High Availability
Architecture
Distributed DBMS is usually a shared nothing architecture Parallel DBMS can be shared-memory, shared-disk, or shared-nothing architecture
Connectivity
Distributed DBMS- Can be connected using public-purpose network, e.g., Internet Parallel DBMS -Machines connects with dedicated high-speed LANs and switches
Communication cost
Distributed DBMS- Communication cost and problems cannot be ignored Parallel DBMS -Communication cost is assumed to be small
Management of distributed data with different levels of transparency like network transparency, fragmentation transparency, replication transparency, etc. Increase reliability and availability Easier expansion Reflects organizational structure database fragments potentially stored within the departments they relate to Local autonomy or site autonomy a department can control the data about them (as they are the ones familiar with it) Protection of valuable data if there were ever a catastrophic event such as a fire, all of the data would not be in one place, but distributed in multiple locations Improved performance data is located near the site of greatest demand, and the database systems themselves are parallelized, allowing load on the databases to be balanced among servers. (A high load on one module of the database won't affect other modules of the database in a distributed database) Economics it may cost less to create a network of smaller computers with the power of a single large computer Modularity systems can be modified, added and removed from the distributed database without affecting other modules (systems) Reliable transactions - due to replication of the database Hardware, operating-system, network, fragmentation, DBMS, replication and location independence Continuous operation, even if some nodes go offline (depending on design) Distributed query processing can improve performance Distributed transaction management Single-site failure does not affect performance of system. All transactions follow A.C.I.D. property: o A-atomicity, the transaction takes place as a whole or not at all o C-consistency, maps one consistent DB state to another o I-isolation, each transaction sees a consistent DB o D-durability, the results of a transaction must survive system failures