Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Tips for Upgrading a Cluster to SQL 2008 - Part 2 Expand / Collapse
Author
Message
Posted Monday, March 19, 2012 10:08 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 11:45 AM
Points: 1,113, Visits: 582
Comments posted to this topic are about the item Tips for Upgrading a Cluster to SQL 2008 - Part 2

Alejandro Pelc
Post #1269332
Posted Tuesday, March 20, 2012 1:48 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, August 16, 2016 2:24 AM
Points: 36, Visits: 643
In this case, the only difference is that after performing the upgrade, the setup process automatically fails over the resources to another node.

Doesn't the setup automatically fail over the resources before the upgrade?


That was the case on my environment, so if that’s the case on yours too it’s time to install the service pack for SQL 2008.

It's a good idea to slipstream the SPs into the main installation, so that you don't need to install them separately.
Post #1269381
Posted Tuesday, March 20, 2012 6:12 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Wednesday, August 17, 2016 6:18 AM
Points: 1,588, Visits: 2,543
Wouldn't have been quicker to slipstream the service pack and performing both the upgrade and the service pack at the same time?

http://blogs.msdn.com/b/petersad/archive/2009/02/25/sql-server-2008-creating-a-merged-slisptream-drop.aspx
Post #1269474
Posted Tuesday, March 20, 2012 7:04 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 11:45 AM
Points: 1,113, Visits: 582
That is completely true, it would have been quicker if I slipstream the service pack into the installation files. I didn't face it that way because not all companies follow the same patch level rules and procedures, so I wanted to separate the process into Upgrade and the Update.

Thanks,
Alejandro


Alejandro Pelc
Post #1269516
Posted Tuesday, March 20, 2012 9:01 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, August 29, 2015 3:10 PM
Points: 9, Visits: 203
Thank you for sharing Alejandro.
Post #1269628
Posted Wednesday, March 21, 2012 7:32 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, September 7, 2012 8:27 AM
Points: 68, Visits: 284
You completed with:
At this point, all passive nodes has the service pack installed and it’s time to perform the update on the active node (serverA), so connect to it and perform the installation of the service pack. The process won’t be different at all as the one on the other nodes as we’ll update one instance at the time. Once the three instances were updated, the SQL Instances 1, 2 and 3 are at the same patch level on all nodes.

Question:
Did you fail over to another server first before upgrading the final server?


*****


Give a man a fish, and you've given him a meal. Teach a man to fish and he'll ask to borrow your boat.
Post #1270154
Posted Wednesday, March 21, 2012 7:43 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 11:45 AM
Points: 1,113, Visits: 582
Hi Eric,
No, I didn't fail over the resources on the last server. That will be handled by the service pack installation process as it will failover automatically the instances, so there's no need to do it manually.

Regards,
Alejandro


Alejandro Pelc
Post #1270163
Posted Monday, June 6, 2016 2:10 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, August 23, 2016 2:53 PM
Points: 1, Visits: 152
Hi Alejandro,
Thanks for this nice post. However I have few questions. I have active/active two nodes cluster setup with one node SQL Server 2008 R2 and the other node SQL Server 2005. Now the application manager wants me to upgrade the SQL 2005 node to SQL 2008 R2. The databases on 2005 instance are having Compatibility Level of SQL 2000 and he does not want to change that so databases will still be SQL 2000 even after SQL upgrade to 2008 R2.
In this scenario I think in-place upgrade is the only option I have. But what is the biggest risk? AND Does in-place upgrade process will also upgrade my databases to 2008 R2 level?
Note: OS is Windows 2008 R2 on both nodes.
Post #1792548
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse