Scribd Logo
Upload

Welcome to Scribd!

  • 1K views

    Types of Distributed Databases.: Homogeneous Distributed Databases System Heterogeneous Distributed Database System

    Uploaded by

    Adiba khan
    The document describes different types of distributed database systems and their architectures. There are two main types: homogeneous which uses the same DBMS software across databases, and heterogeneous which uses different DBMS software. Common architectures include client-server with single or multiple servers, peer-to-peer, and multi-DBMS. The document also discusses design alternatives for data distribution including non-replicated/non-fragmented, fully replicated, partially replicated, fragmented, and mixed approaches.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Types of Distributed Databases.: Homogeneous Distributed Databases System Heterogeneous Distributed Database System

    Uploaded by

    Adiba khan
    1K views22 pages
    The document describes different types of distributed database systems and their architectures. There are two main types: homogeneous which uses the same DBMS software across databases, and heterogeneous which uses different DBMS software. Common architectures include client-server with single or multiple servers, peer-to-peer, and multi-DBMS. The document also discusses design alternatives for data distribution including non-replicated/non-fragmented, fully replicated, partially replicated, fragmented, and mixed approaches.

    Original Description:

    in this document ........

    Original Title

    database lecture

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document describes different types of distributed database systems and their architectures. There are two main types: homogeneous which uses the same DBMS software across databases, and heterogeneous which uses different DBMS software. Common architectures include client-server with single or multiple servers, peer-to-peer, and multi-DBMS. The document also discusses design alternatives for data distribution including non-replicated/non-fragmented, fully replicated, partially replicated, fragmented, and mixed approaches.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    1K views22 pages

    Types of Distributed Databases.: Homogeneous Distributed Databases System Heterogeneous Distributed Database System

    Uploaded by

    Adiba khan
    The document describes different types of distributed database systems and their architectures. There are two main types: homogeneous which uses the same DBMS software across databases, and heterogeneous which uses different DBMS software. Common architectures include client-server with single or multiple servers, peer-to-peer, and multi-DBMS. The document also discusses design alternatives for data distribution including non-replicated/non-fragmented, fully replicated, partially replicated, fragmented, and mixed approaches.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 22

    Types of distributed

    databases.
    The two types of distributed systems are as
    follows:
    • Homogeneous distributed databases system
    • Heterogeneous distributed database system
    Homogeneous distributed databases system

    • Homogeneous distributed database system is a network of two or more


    databases (With same type of DBMS software) which can be stored on one or
    more machines.
    • So, in this system data can be accessed and modified simultaneously on several
    databases in the network. Homogeneous distributed system are easy to handle.
    • Example: Consider that we have three departments using Oracle-9i for DBMS.
    If some changes are made in one department then, it would  update the other
    department also.
    Heterogeneous distributed database system

    • Heterogeneous distributed database system is a network of two or more


    databases with different types of DBMS software, which can be stored on
    one or more machines.
    • In this system data can be accessible to several databases in the network
    with the help of generic connectivity (ODBC and JDBC).
    • Example: In the following diagram, different DBMS software are
    accessible to each other  using ODBC and JDBC.
    Distributed DBMS Architectures
    DDBMS architectures are generally developed depending on three
    parameters −
    • Distribution − It states the physical distribution of data across
    the different sites.
    • Autonomy − It indicates the distribution of control of the
    database system and the degree to which each constituent DBMS
    can operate independently.
    • Heterogeneity − It refers to the uniformity or dissimilarity of the
    data models, system components and databases.
    Architectural Models

    Some of the common architectural models are −


    • Client - Server Architecture for DDBMS
    • Peer - to - Peer Architecture for DDBMS
    • Multi - DBMS Architecture
    Client - Server Architecture for DDBMS
    This is a two-level architecture where the functionality is divided
    into servers and clients. The server functions primarily
    encompass data management, query processing, optimization and
    transaction management. Client functions include mainly user
    interface. However, they have some functions like consistency
    checking and transaction management.
    • The two different client - server architecture are −
    • Single Server Multiple Client
    • Multiple Server Multiple Client (shown in the following
    diagram)
    Peer- to-Peer Architecture for DDBMS
    In these systems, each peer acts both as a client and a server for imparting
    database services. The peers share their resource with other peers and co-
    ordinate their activities.
    • This architecture generally has four levels of schemas −
    • Global Conceptual Schema − Depicts the global logical view of data.
    • Local Conceptual Schema − Depicts logical data organization at each
    site.
    • Local Internal Schema − Depicts physical data organization at each site.
    • External Schema − Depicts user view of data.
    Multi - DBMS Architectures
    • This is an integrated database system formed by a collection of two or more
    autonomous database systems.
    • Multi-DBMS can be expressed through six levels of schemas −
    • Multi-database View Level − Depicts multiple user views comprising of
    subsets of the integrated distributed database.
    • Multi-database Conceptual Level − Depicts integrated multi-database that
    comprises of global logical multi-database structure definitions.
    • Multi-database Internal Level − Depicts the data distribution across different
    sites and multi-database to local data mapping.
    • Local database View Level − Depicts public view of local data.
    Local database Conceptual Level − Depicts local data organization at each
    site.
    Local database Internal Level − Depicts physical data organization at each
    site.

    • There are two design alternatives for multi-DBMS −


    • Model with multi-database conceptual level.
    • Model without multi-database conceptual level.
    Design Alternatives

    • The distribution design alternatives for the tables in a DDBMS are as


    follows −
    • Non-replicated and non-fragmented
    • Fully replicated
    • Partially replicated
    • Fragmented
    • Mixed
    Non-replicated & Non-fragmented
    • In this design alternative, different tables are placed at different
    sites. Data is placed so that it is at a close proximity to the site
    where it is used most. It is most suitable for database systems
    where the percentage of queries needed to join information in
    tables placed at different sites is low. If an appropriate
    distribution strategy is adopted, then this design alternative
    helps to reduce the communication cost during data processing.
    Fully Replicated
    • In this design alternative, at each site, one copy of all the database
    tables is stored. Since, each site has its own copy of the entire
    database, queries are very fast requiring negligible
    communication cost. On the contrary, the massive redundancy in
    data requires huge cost during update operations. Hence, this is
    suitable for systems where a large number of queries is required
    to be handled whereas the number of database updates is low.
    Partially Replicated
    • Copies of tables or portions of tables are stored at different
    sites. The distribution of the tables is done in accordance to the
    frequency of access. This takes into consideration the fact that
    the frequency of accessing the tables vary considerably from
    site to site. The number of copies of the tables (or portions)
    depends on how frequently the access queries execute and the
    site which generate the access queries.
    Fragmented
    • In this design, a table is divided into two or more pieces referred to as
    fragments or partitions, and each fragment can be stored at different sites.
    This considers the fact that it seldom happens that all data stored in a table
    is required at a given site. Moreover, fragmentation increases parallelism
    and provides better disaster recovery. Here, there is only one copy of each
    fragment in the system, i.e. no redundant data.
    • The three fragmentation techniques are −
    • Vertical fragmentation
    • Horizontal fragmentation
    • Hybrid fragmentation
    Mixed Distribution

    • This is a combination of fragmentation and partial


    replications. Here, the tables are initially fragmented in
    any form (horizontal or vertical), and then these
    fragments are partially replicated across the different
    sites according to the frequency of accessing the
    fragments.

    You might also like