replication for dual schemas in same database [message #561095] |
Wed, 18 July 2012 15:27 |
|
Kevin Meade
Messages: 2103 Registered: December 1999 Location: Connecticut USA
|
Senior Member |
|
|
Hi all. I was asked for ideas to do a certain type of replication. I still have questions out to people for why they want to do this; eg. what problems are they trying to solve etc. But in the mean time I would like to hear from anyone who has actually done this before so that I can evaluate what has worked for you. I have been asked about:
creating two schemas in the same database which are duplicates of each other. One schema will be live and the other readonly. A reporting process will read off the readonly schema while changes are made to the live schema.
(so far so good, but here is the catch):
At some point, the application wants to swap schemas. This means making schema A readonly, then resynching schema B to schema A, then making schema B the live schema. the assocatied applications will now do their things by swapping their use of the schemas. This sounds unusual to me. I can't figure out at the moment the value of "swapping" so I have asked that question to my people here at work as to why they think they need this.
In the meantime I am asking you, has anyone done this? If so how did you achieve it? What would you like to offer up as significant observations about your solution, particularly if you felt is did what it was supposed to do (which was what by the way?)?
I am familiar with all of the following:
materialized views
master/master replication
CDC
SHAREPLEX
GOLDEND GATE
home grown trigger based replication
historical schemas I am really again asking for your experiences with this dual schema design.
Thanks, Kevin
[Updated on: Wed, 18 July 2012 15:28] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|