March 31, 2009 at 10:57 am
Hi,
I am newbie implementing replication. I have the following system 2 SQL 2008 Workgroup Edition one will be my publisher and one will be my subscriber on a Transactional Replication. A third party application is inserting and updating my Publisher server this application can have a backup server to stored the information in case of a failure on the primary server. I am planing to used the Subscriber as a backup server. This third party application will stay inserting and updating data to the backup server until I manually switch it back. So I now need to sent the information back to the Primary server which is my publisher. I know what is data so I can query and insert the data back to the Primary server by linking the servers, but how do i tell the publisher not to insert those records back to the subscriber because they are already there.
Is this posible ? Is there any way to indicate a starting point for Transactional Replication so only changes from that point on will be replicated back to the subscriber.
Thanks
jdelgado
March 31, 2009 at 11:13 am
You basically have two options.
The first is merge replication as this allows you to update either system and feed the changes back to the publisher.
The second is that in the event of a failure you switch to the backup system. After the primary system is repaired you remove the replication and configure replication using the backup server as the publisher feeding data to the primary server. At this point your backup server is now your primary server.
Then in the event that your server which is now your primary server fails you simply repeat the process.
I would recommend the transactional option; while it requires a little more work to reconfigure in the event of a failure, transactional replication is easier to keep running than merge replication.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply