Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Replication & Patches

Status
Not open for further replies.

NickCorlett

Technical User
May 23, 2002
71
GB
I am trying to identify the best practice for installing patches on two servers which are running continuous transactional replication. One server is the publisher and distributor with the other being the subscriber.

Should I be pausing replication for the period during which the install takes place on both the publisher and subscriber. Should I delete the subscriptions altogether and then re-initialise once the install is complete.

I am asking because I experienced a problem when the publisher/distributor was re-booted for a patch install and the subscriber fell-over complaining that it couldn't contact the publisher and never got back on it's feet again until I deleted and re-created the subscription.
 
I generelly stop the replication jobs before installing SQL patches. Knock on wood, I've never had any problems before.

It could have been the way that the patch stopped and restarted the SQL Server. The patch may not account for the replication having to stop before stopping the SQL Service.

Denny

--Anything is possible. All it takes is a little research. (Me)

[noevil]
(My very old site)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top