Hi Sebastian,
Attached You will find a picture of our concept configuration. We want
to use Sequoia as a front end to put several different DBs behind it,
with different irror solutions. We assume that we can achieve our goal
only with a nested sequoia configuration, like the picture shows.
Do you think this can be all achieved only through a RAIDb-2
configuration?
If what you want is aggregate all your databases to present them as a
single database but still have some replication you should go for a
RAIDb-2 configuration. Just put all databases in the same RAIDb-2
virtual database, the controller will detect automatically the db
schemas available on each backend and update the databases as needed.
Be careful that in that scenario, table names must be different for each
database (Tubis, DB1, DB2 and DB3). Also you will not be allowed to use
fully qualified names in your queries (such as SELECT DB1.x WHERE
DB2.x=DB3.y).
Finally RAIDb-2 as the same limitations as RAIDb-0, the main one being
that distributed joins are not supported. Therefore, you will not be
able to do a select on multiple databases at once.
I would recommend using multiple schemas inside the same database rather
than multiple databases if your application design allows it.
Hope this helps,
Emmanuel
--
Emmanuel Cecchet
Chief Architect, Continuent
Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
