1. Propagation will happen according to the frequency of your PUSH job.
2. Any DML that is committed is propogated
3. Configure multi-master advanced replication - you could replicate between 1024 databases!
4. same as question two. Whether replication is "hogging the network bandwidth" depends on the transaction level and how fat the pipe is.
It's getting stream lined to the MultiMaster replication: Now to clarify
On DB-2 only dataloads will happen (on 3 tables) and this has to be replicated to DB-1.
DB-1 is the MAIN production database with these 3 tables also.And also, I don't want the data to be replicated from DB-1 to DB-2. Is that possible to have a multimaster but only in one direction.
"ALSO, VERY IMPORTANT: know that if you do not propogate changes on one of the sites, your master sites are OUT-OF-SYNC! What does this mean to your business??? "
These are Master tables(Inventory) which will be replicated from DB-2 to DB-1.
So having them 'out of sync' is acceptable.
One more question:
What will happen, If you have a table on DB-1 and try to have a snapshot replication enable between DB-1 and DB-2. What ever changes happen on DB-2 be refreshed to DB-1. Can the snapshot replication be enabled....as I already have the tables in the DB-1.