DistributedDatabaseDesignSemanticDataControl.pptVIP

P. Brezany Distributed Database Design Semantic Data Control Univ.-Prof. Dr. Peter Brezany Institut für Scientific Computing Universit?t Wien Tel. 4277 39425 Sprechstunde: Di, 13.00-14.00 LV-Portal: www.par.univie.ac.at/~brezany/teach/gckfk/06ss/300658.html Distributed Database Design A General Framework Considered in the Distributed Database Design Problem A General Framework Considered in the Distributed Database Design Problem (2) Alternative Design Strategies Top-Down approach Bottom-Up approach In most database designs, the two approaches may need to be applied to complement one another. It is a joint function of the database, enterprise, and application system administrators (or of the administrator performing all three roles) Top-Down Design Process Bottom-Up Design Process Top-down design is a suitable approach when a database system is being designed from scratch. Commonly, a number of databases already exist, and the design task involves integrating them into one database. ? the bottom-up approach is suited for this type of environment. The starting point is individual local conceptual schemas. The process consists of integrating local schemas into the global conceptual schemas. This type of environment exists primarily in the context of heterogeneous databases. Distribution Design Issues - Fragmentation Why fragment at all? How should we fragment? How much should we fragment? Is there any way to test the correctness of decomposition? How should we allocate? What is necessary information for fragmentation and allocation? Reasons for Fragmentation The important issue is the appropriate unit of distribution: a relation is not a suitable unit – why? Application views are usually subsets of relations, therefore the locality of accesses of applications is defined not on entire relations but on their subsets ? it is only natural to consider subsets of relations as distribution units. If the applications that have views defined on a given relation resid