I want to design a model for a distributed database solution.
- Are there appropriate tools and approaches?
- How to include stereotypes for (horizontal) fragments?
I want to design a model for a distributed database solution.
|
|||||||||
|
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, see the FAQ.
If you are looking for data models to start with, I'd recommend you take a look at: http://www.databaseanswers.org/data_models/index.htm This is the most comprehensive list of data model examples that I found so far. In fact I have used some samples as starting point for some of my projects. These models won't show you how to take horizontal fragmentation into consideration, though. Update: You may consider these basic techniques for horizontal fragmentation*:
*Source - Distributed Database Systems: Fragmentation and Allocation by Katja Hose, Ralf Schenkel |
|||||||||||
|