Snapshot Replication 1

[JohnBates]

Hi everyone,

I'm exploring the 3 types of replication. i've used merge and snapshot in the past.

I really only need for changes for 2 tables to get replicated to Server B. Don't need bi-directional.... changes on Server B do not need to be replicated to Server A. Just need changes to be sent maybe twice per day.. not really real-time.

I think snapshot repl has to send the entire table rather than only changes/inserts/deletes. Am I correct?

I'm hoping to avoid the more complex transactional and merge types if possible.

Thanks, John

 

[camy123]

yep that is the best one other replications such as transactional is ok but would not be best suited as it consumes network traffic i would fo with snapshot.

 

[JohnBates]

thanks for the info camy123 !

You replied to my other post relating to merge-replication.

What I really need is to setup merge for Table1 and setup a snapshot for Table2. Table2 would only be pushed down to the other server twice per week.

But I know that merge also requires a snapshot.

... so do you know if I can use TWO snapshots ? Would the
snapshot for Table2 get in the way of the snapshot required for Table1 (the merge table) ?

Thanks for your opinions. I appreciate your advice. John

 

[camy123]

please forgive me for being thick but if you are using merge replication then why do you need snapshot beacuse the databases/tables will rarely be out of sync.

you only need one replication method using more then one on the same tables can be very messy but there is no rule that u cant ... but be carefull if you dont need to do it then dont bother as it does increase performance problems.

aplogies in advance if i got the wrong end of the stick

but i personally would'nt use merge and snapshot Stick to one which is best for you.

 

[JohnBates]

No cam123 you're not thick.

We would be using merge on Table 1 and snapshot (say a daily push) on Table2. Table2 would not be merged...updates, if they did occur on Server2, would not need to be replicated up to Server1. Just need to periodically 'refresh' the Table2 data on Server2.

As for merge, I have experienced 'synchronization conflicts' on the merge table. Even tho I had chosen Server1 (the publisher) as the winner of any conflict... we sometimes lost a row for the merge table on Server1.

Thanks, John

 

[camy123]

ok Mate heres the Deal....

what you should do is create 2 publications on the source database for table 1 and table 2
when creating the publication select merge and therfore it will meree with the associated subscriber you set.

for publication 2 set snapshot and then again set up the subscirbe with push once daily that will do the trick ive just done it had it running for 6 hors no conflicts
hope this helps mate.