How to deploying SQL Server 2005 SP3 Cumulative Update 5 9.00.4230 on Active/Active cluster with each node having different version of SQL Server.

  • sivaprasad

    SSCertifiable

    Points: 6183

    How to deploying SQL Server 2005 SP3 Cumulative Update 5 9.00.4230 on Active/Active cluster with each node having different version of SQL Server.

    Node1:

    Microsoft SQL Server 2005 - 9.00.4220.00 (X64) Apr 2 2009 18:34:24

    Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

    Node 2:

    Microsoft SQL Server 2005 - 9.00.4262.00 (X64) Aug 13 2009 17:06:39

    Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

    Now client wants to have SQL Server 2005 SP3 Cumulative Update 5 9.00.4230 on Active/Active cluster.

    On one node i.e., Node 2 already running on higher version.

    What are the best possible way to bring the SQL Server instances into consistent version on both nodes?

    Can we uninstall the Microsoft SQL Server 2005 - 9.00.4262.00 (X64) from the node where it has installed? Followed by installation of Cumulative Update 5 9.00.4230.

    Sivaprasad S - [ SIVA ][/url]http://sivasql.blogspot.com/[/url]

  • abair34

    Ten Centuries

    Points: 1055

    It looks like you have node 1 running the SP3 CU3 Binaries

    and node 2 running SP3 CU3 + a QFE hotfix (KB970894)

    You don't want your nodes to have different version running.

    Personally I would make sure the instance is running on node 2 and I would uninstall KB970894.

    Then I would try to install SP3 CU5. Make sure you're logged in on the console when you run it and that nobody is RDP'ed into either node.

    If for some reason you have an issue where the install fails on the step where its trying to update the passive node you may need to go to the cluster properties and remove the passive node from the possible owners list and then run the install again. Then add back the possible owner, fail over to it, remove the node that you just service packed from possible owners and run the install package again.

    Goodluck.

Viewing 2 posts - 1 through 2 (of 2 total)

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