A step-wise distributed database design methodology, Database Management System

A step-wise distributed database design methodology

Following is a step-wise methodology for distributed database design.

(1) Examine the nature of distribution. Find out whether an organisation requires having a database at each branch office, or in every city, or possibly at a regional level. It has direct implication from the viewpoint of  fragmentation.   For example, in case database is needed at each branch office, the relations may fragment on the basis of branch number.

(2) Create a detailed global E-R diagram, if so needed and classify relations from entities.

(3) Analyse the most significant transactions in the system and classify where horizontal or vertical fragmentation may be desirable and helpful.

(4) Classify the relations that are not to be fragmented. Such relations will be replicated everywhere. From the global ER diagram, eliminate the relations that are not going to be fragmented.

(5) Study the relations that are on one-side of a relationship and choose a suitable fragmentation schema for these relations. Relations on the many-side of a relationship might be the candidates for derived fragmentation.

(6)  During the earlier step, check for situations where either vertical or mixed fragmentation would be required, that is, where the transactions need access to a subset of the attributes of a relation.

 

Posted Date: 3/13/2013 8:47:42 AM | Location : United States







Related Discussions:- A step-wise distributed database design methodology, Assignment Help, Ask Question on A step-wise distributed database design methodology, Get Answer, Expert's Help, A step-wise distributed database design methodology Discussions

Write discussion on A step-wise distributed database design methodology
Your posts are moderated
Related Questions
What are the two integrity rules?  Ans:  The two integrity rules are: Entity Integrity Rule & Referential Integrity Rule.   Entity Integrity Rule - If the attribute A of rel

Define functional and multivalued dependencies.       Ans:  A functional dependency is a assets of the semantics of the attributes in a relation. The semantics point out how at

What are the basic objects of the data dictionary? Tables Domains Data elements Structures Foreign Keys

File Organisation In Dbms Introduction Databases are used to store information. Usually, the principal operations we have to perform on database are those relating to:

Why DML is used for? DML is used to Manipulation and processing of database. DML is provided for manipulation & processing of database. (Data stored in the database is processed

What are the three data anomalies that are likely to occur as a result of data redundancy?  Can data redundancy be completely eliminated in database approach?  Why or why not? A

Mention the several levels in security measures. A) Database system B) Operating system C) Network D) Physical Human

Define Assertions in SQL a. An assertion is a predicate that is expressing a condition we wish the database to always satisfy.  b. Domain constraints, functional dependency

What is trigger Triggers are statements that are implemented automatically by the system as the side effect of a change to the database.

Which database object does not physically exist? A view database object does not physically exist.