all groups > sql server replication > april 2004 >
You're in the

sql server replication

group:

2 types of replication of the same database


Re: 2 types of replication of the same database Hilary Cotter
4/7/2004 8:14:57 AM
sql server replication:
I concur with Paul, use transactional over snapshot except when large
amounts of data change at infrequent intervals. Otherwise use transactional
as it is more scalable and a better solution for low bandwidth lines as only
new transactions flow across the lines to the Subscribers.
[quoted text, click to view]

2 types of replication of the same database Howzit
4/7/2004 11:03:20 AM
I have a database of approx 700mb that I want to replicate to one of our
regional offices.

I would like to know if it is adviseable to split the database into 2 types
of replications.
1. Merge
2. Snapshot.

The reason for 2 types of replication is that I do not require all the data
to be merged, and some tables will only be updated at head office and not at
the regional office.

Would this work?

Re: 2 types of replication of the same database Paul Ibison
4/7/2004 11:13:31 AM
Howzit,

Splitting up the articles into 2 publications will work only if the 2 sets
of articles aren't related. If you can group related tables together then
you won't have PK/FK violation errors.

If above point is valid, then for the data only updated at HO, you have to
consider the size of the tables and the latency you are prepared to accept.
Usually you would use transactional replication for this scenario. There is
low latency, you are not blocking your users on the subscriber when
transactional data is transferred, the initial snapshot doesn't have to lock
the tables on the publisher, it is faster etc. For data which can be updated
in more than one place, I agree that merge is a good option as there is a
big range of conflict resolvers and you can have autonomy if needed.

Regards,
Paul Ibison

AddThis Social Bookmark Button