Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
chadmat
The Chadinator
1974 Posts |
 Posted - 2002-03-06 : 00:43:14
|
| Okay folks this is my first question on this board.I have a situation, and I wanted to see if anyone has done such a design before?I am faced with the problem of needing bidirectional replication between two different schemas. Background is we are going to be re-architecting a large enterprise application module by module with the new schema vastly different than the original and will need both schemas active until all modules have been completed. This is because a user may do work in Module (M) 1 and M2 in the old schema but do work in M3 in the new schema until M1 and M2 have been released in the new schema. One requirement is not making changes to the original application short of turning on replication. Our current thinking is turn on replication (merge or updateable transaction) in both schema 1 and schema 2 and have a custom process move the changes between the replicated versions of the schemas. Having replication on schema 2 allows us to just turn off replication without doing anything else to the production database when version 1 of the application is finally retired.Anyone have any ideas on this?-Chad |
|
|
|
|
|
Bidirectional Replication