Enterprise Replication : Restrictions
Posted in 2004
Topics: High Availability & Replication
Hello, I have 2 questions when using Enterprise Replication : 1 - In the case of consolidation, is it possible to replicate table from the primary to table from the target which will have one column more containing the name of the primary. It is useful when we have a lot of primary sending to only one target. 2 - Is it possible to replicate 2 differents tables from the primary to a unique table from the target which will have merges all column from the 2 differents tables. Regards, Bj
"Bj" <Bruxelles.Jette@caramail.com> wrote in message news:89d8947b.0405050706.60fcf7c3@posting.google.com... > Hello, > > I have 2 questions when using Enterprise Replication : > > 1 - In the case of consolidation, is it possible to replicate table > from the primary to table from the target which will have one column > more containing the name of the primary. It is useful when we have a > lot of primary sending to only one target. No - The column and data on the source must match the target. However, if you define the replicated table as update anywhere, then you can take advantage of the shadow columns which contain the identity of the location of the last update. > > 2 - Is it possible to replicate 2 differents tables from the primary > to a unique table from the target which will have merges all column > from the 2 differents tables. > Yes. The participants of replication can have two tables on the source merging into a single table on the target - as long as the primary keys are unique and the columns all map. This is a bit unusual - but I see no reason that it can't be done. > Regards, > Bj