Re: Multi-Master Replication

Simo Silmu schreef:
Hi there,

I am planning a multi-master replication which should work like this:

we have two databases (version is 10.2) and from db1 we would like to push all changes to db2. From db2 we would like to replicate only changes concerning two tables to db1.

Any ideas how I should approach this. Do I need to create two replication groups.

Any help would be appreciated or links to similar setup

rgds
SS


You set up MM replication for the two tables,
and MS replication for everything else.
I'd suggest you take a look a Streams, judging
by the version you're at. Streams is the successor
of Advanced Replication, and has been around since
9iR2, and is mature enough in 10R2
--
Regards,
Frank van Bortel

Top-posting is one way to shut me up...
.

Relevant Pages

  • Re: Table Synchronization across databases on the same server
    ... > inhouse application which maintains a transactional database, DB2 also ... Since the DB1 is frequently updated the ... Anyway, I'm not very good at replication myself, I would encourage you to ...
    (comp.databases.ms-sqlserver)
  • Re: Table Synchronization across databases on the same server
    ... Triggers will add to the overhead of the application which uses DB1. ... should be able to use log shipping or transactional replication for what you ... you will be unable to update tables on db2. ...
    (microsoft.public.sqlserver.replication)
  • Re: Inactive Transaction/Log will not truncate after replication disabled
    ... I am a little confused by this statement "I decided to disable/remove all ... on DB1, and writing to the distribution database on DB2. ... from what you describe that you have disabled replication ... > disable/remove all replications setup via Enterprise Manager. ...
    (microsoft.public.sqlserver.replication)
  • Transactional replication: Deadlock issue
    ... I have a replication setup like ... replication, it shows that there is some sort of deadlock situation ... copying the data from DB1 to DB2(as reinitializing from scratch will ... erase the data in DB2 and also DB3) create a new subscription at DB2. ...
    (microsoft.public.sqlserver.replication)
  • Inactive Transaction/Log will not truncate after replication disabled
    ... I set up a transactional replication from 'DB1' at node A ( ... scheduled transaction backup run. ... I set up the push replication at 'DB1' with published article 'T' and not ... noticed that the Transaction Log in the 'DB1' keep growing even after log ...
    (microsoft.public.sqlserver.replication)