Apply service pack 3 to servers in replication

  • Hi All,

    We have peer to peer replication set up between 2 servers. We are planning to apply SP 3 to both these Servers.

    MY Plan is to

    Stop all applications and services that make connections to the instance being upgraded

    Stop the Replication jobs on both the servers.

    Backup the system databases and user databases.

    Install SP3

    Reboot the Sql Server Box

    Double check all error log files

    Perform some basic system tests

    Perform db Maintenance (DBCC Checks)

    Start replication job on both the servers

    Start the applications

    Verify proper operation of client applications.

    Do the same Process on the second instance as well.

    can you guys please let me know if the process is right. If not Please correct me.

  • Your plan look ok to me..

    I have have in the past where installing a SP or CU breaks P2P replication, but not in all cases.

    One thing I would add is to install the latest CU. http://support.microsoft.com/kb/960598

    It has some P2P fixes in it.

    In addition, I would test in a stage environment 1st (if possible).

  • It's very easy believe me. You planning to stop SQL Services also?

    No need to stop any applications while you are applying SP.

    Turn off replication on both servers.

    Make sure full back up is complete.

    Reboot servers.

    Apply SP

    Reboot servers.

    Turn on replication.

    EnjoY!

    EnjoY!
  • How did this upgrade go?

    I have to upgrade two SQL Server 2005 servers participating in transactional replication with updates at the subscriber. I will be starting from build 9.0.3042.

    I read somewhere that instances should be upgraded in the order Distributer, Publisher, Subscribers, but apart from that is it really as simple as GTR says?

    Any feedback will be greatly appreciated!

  • DPS is the right order

    starting with SP2, the install has been very nice. it even updates both cluster nodes with one install. we did have an issue one time where SQL server agent wouldn't start on a cluster but a call to PSS fixed it

  • andrewba (4/29/2010)


    How did this upgrade go?

    I have to upgrade two SQL Server 2005 servers participating in transactional replication with updates at the subscriber. I will be starting from build 9.0.3042.

    I read somewhere that instances should be upgraded in the order Distributer, Publisher, Subscribers, but apart from that is it really as simple as GTR says?

    Any feedback will be greatly appreciated!

    For Transactional Replication the order should be: Distributor -> Subscriber -> Publisher

  • The 2005 SP3 release notes agree with alen - the upgrade order should be D, P, S. See http://download.microsoft.com/download/5/7/1/5718A94A-3931-457B-8567-AA0995E34870/ReleaseNotesSQL2005SP3.htm

  • andrewba (5/2/2010)


    The 2005 SP3 release notes agree with alen - the upgrade order should be D, P, S. See http://download.microsoft.com/download/5/7/1/5718A94A-3931-457B-8567-AA0995E34870/ReleaseNotesSQL2005SP3.htm%5B/quote%5D

    You are correct. Sorry for the bad info. My info was from an old 2591A course manual. I guess it's changed since then.

  • Hi

    My upgrade went fine without any Hiccups.

    thanks

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply