June 4, 2009 at 12:00 pm
my primary server is going offline for 60 mins this weekend for maintenance. It is replicated to a 2nd server.
I dont want to stop replication, as this means a resync will be required afterwards, and that takes many hours.
Is there a method of "pausing" replication, or can i just leave it alone and it will sort itself out after the main server comes back up?
June 5, 2009 at 3:03 am
This shouldn't be a problem.
No need to stop/pause replication. Only if you use transactional repl with immediately updating subscribers, you won't be able to make any changes on the subscriber while your primary server is offline.
[font="Verdana"]Markus Bohse[/font]
June 5, 2009 at 3:24 am
Wow 60 minutes, you are lucky winston, never had that window to do something, As marcus suggested, until there is a transcation on the primary server the logs, it will not take longer to sync, shouldn't be a problem
June 5, 2009 at 4:15 am
It is transactional replication, but its at the weekend during a maintenance window, a time during which we are allowed take the system down so there are usually zero users on the publishing system or the subscribing systems.
Thanks for the advice folks, much appriciated. Folk here are always super helpful and its nice to see people helping just for the sake of helping, not looking for reward!
All the best.
June 5, 2009 at 4:38 am
Check out:
http://www.sqlservercentral.com/Forums/Topic429161-291-1.aspx
http://www.sqlservercentral.com/Forums/Topic429161-291-2.aspx
http://social.msdn.microsoft.com/forums/en-US/sqlreplication/thread/ffcfa9d2-d295-404c-be78-02a0138798e3/%5B/url%5D
http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/e0fbaec7-fcb1-4860-9377-34dcd8e3db9f/%5B/url%5D
Tanx 😀
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply