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

sql server replication

group:

Merging data before replication


Merging data before replication Leila
4/28/2006 12:00:00 AM
sql server replication:
Hi,
One application is running in two different locations. The database
structure is the same for both. Each database has its own data. For
replication, I cannot apply snapshot of one to the other because the target
will loose its data. I was thinking of exporting their data to an
intermediate(shared) database and then replace each db with this new one
(Assuming the PKs will remain unique).
I'm sure I'm not the first person who has encountered with this situation,
therefore there must be a known solution!
Any help would be greatly appreciated.
Leila

Re: Merging data before replication Paul Ibison
4/28/2006 12:00:00 AM
Leila,
why not simply use merge replication?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Re: Merging data before replication Leila
4/28/2006 12:00:00 AM
Thanks Paul,
Merge is the option I want ot use. But how can I append each database's data
to the other?


[quoted text, click to view]

Re: Merging data before replication Paul Ibison
4/28/2006 12:00:00 AM
Ah - I see the problem now. In this type of scenario I decide which is to be
the publisher and use Redgate's Datacompare to compare this with the
subscriber database and to create the amalgamation script. After that I
initialize from the publisher to the subscriber.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)




AddThis Social Bookmark Button