Hi,
I'm having some problems restoring replication and hope someone here can help.
Here's the situation. Basically we have a central server that acts as the publisher and distributer for a merge replication, and a bunch of clients that subscribe to it. This has been running for a few years, so the client databases all have the correct table structures.
We had some issues that forced us to replace all the database servers, SQL2005 on the publisher and SQL2000 on the subscribers. The central server was out of commission for a few weeks, so there's now a big difference in the data on it vs. that on the subscribers.
My problem is getting the replication going without losing the data that's been entered at the subscribers. I can create subscriptions on the new server, but when I initialize them on my test server all the data on the subscriber that the publisher doesn't have is lost. If I push it without initializing the synchronization seems flakey. The outstanding data on the subscriber isn't pulled back and updates on the publisher don't always update on the subscriber.
As you can probably tell at this point, I'm a programmer not a DBA, but my company doesn't want to spend for one so this was handed to me. Can somebody point me in the right direction?
Thanks,
Pat
I'm having some problems restoring replication and hope someone here can help.
Here's the situation. Basically we have a central server that acts as the publisher and distributer for a merge replication, and a bunch of clients that subscribe to it. This has been running for a few years, so the client databases all have the correct table structures.
We had some issues that forced us to replace all the database servers, SQL2005 on the publisher and SQL2000 on the subscribers. The central server was out of commission for a few weeks, so there's now a big difference in the data on it vs. that on the subscribers.
My problem is getting the replication going without losing the data that's been entered at the subscribers. I can create subscriptions on the new server, but when I initialize them on my test server all the data on the subscriber that the publisher doesn't have is lost. If I push it without initializing the synchronization seems flakey. The outstanding data on the subscriber isn't pulled back and updates on the publisher don't always update on the subscriber.
As you can probably tell at this point, I'm a programmer not a DBA, but my company doesn't want to spend for one so this was handed to me. Can somebody point me in the right direction?
Thanks,
Pat