abelalston316
jamesonridley
kurtisgolden427
normanvpgonzal
jaysimon717
frenchvisa
iKick_in
andrewilcox25
bobcollins511
https://me.yahoo.com/a/hb...
coychapman716
austin0v
jointy
michealcohen922
andrew91m
oscarharring1026
stacyvazquez48
bradleycolli11
vani123
https://me.yahoo.com/mose...
Steves
impa
Klugger
Dustin
dhara
dotnetfunda
MihirPatel
Alex
TareqOmar
Nickolay
Mark
jch0001
Mike
questpond
jacobsebastian
KMil
http://baldi.myopenid.com/
Andrew
jantu
When working with federations, database schema requires a special consideration.
With federations, you take parts of your schema and scale it out. With each federation in the root database, a subset of objects are scaled-out. You may create multiple federations because distribution characteristics and scalability requirements may vary across sets of tables. For example, with an ecommerce app, you may both have a large customer-orders set of tables and a very large product catalog that may have completely different distribution requirements.
All the schema artifacts in the root and in federation members are scoped to the database. Meaning objects in the root database are only visible when connected to root and objects in the members are only visible in the member. There is no schema enforcement across members of a federation to have exactly matching schema elements. So federation member 1 and 2 may have completely different schema...
iftekharahmedamit
No comments yet, be the first one to post comment.