Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Prepare SQL Server 2005 in a Clustered Environment for SP3 Expand / Collapse
Author
Message
Posted Friday, June 19, 2009 12:29 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 4:34 AM
Points: 425, Visits: 549
Comments posted to this topic are about the item Prepare SQL Server 2005 in a Clustered Environment for SP3

Post #738075
Posted Friday, June 19, 2009 5:06 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, August 28, 2014 12:47 AM
Points: 7,005, Visits: 8,451
First of all thank you for posting these mishaps and the work around.

We didn't encounter these problems when upgrading from sp2 cu2 to SP3 on our 2-node sql-cluster (multiple instances).
We do pay attention for the cluster resource to reside on the same node as the sql instance to be upgraded.
We even upgraded multiple instances in a single run. We moved all instances to the same node before starting the upgrade.

Off course it will not hurt to have a spare/backup set of resource db files !
We take a copy of them after every upgrade (because at that moment is planned downtime).

One thing we did observer is the needed reboot after the first instance + the client software have been upgraded.


Johan


Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere

- How to post Performance Problems
- How to post data/code to get the best help


- How to prevent a sore throat after hours of presenting ppt ?


"press F1 for solution", "press shift+F1 for urgent solution"


Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me
Post #738175
Posted Friday, June 19, 2009 5:28 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 4:34 AM
Points: 425, Visits: 549
It could be that it is hardware related. I've had several people with the same problem but others that didn't have the problem.

Post #738184
Posted Friday, June 19, 2009 5:54 AM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Thursday, August 28, 2014 2:34 AM
Points: 1,454, Visits: 2,982
Thanks for the article we have a test cluster to do this on shortly so we can try it out.

Facts are stubborn things, but statistics are more pliable - Mark Twain
Carolyn
SQLServerSpecialists
Post #738199
Posted Friday, June 19, 2009 7:42 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, August 22, 2014 4:18 AM
Points: 2,048, Visits: 1,403
We've just gone through a cluster migration project and used the approach you outline. One thing you may find is that if you change the startup parameters of SQL Server via Configuration Manager, e.g. change the location of where master.mdf resides, the Config Manager information and the Registry information on each cluster node can get out of synch.
This can be prevented by following the instructions in this link: http://support.microsoft.com/kb/912397

We were migrating to a new server so we also had the problem of the new server containing the old server name when 'SELECT @@servername' was executed. We had to drop the old server name and add a new one.

Another issue is that the msdb subsystems may now be in a different physical location so the contents of the msdb.dbo.syssubsystems table must be deleted and the susbsystems reinitialised using 'EXEC dbo.sp_verify_subsystems 1'

Lastly, if you are moving servers, be sure to backup the Service Master Key and then restore it using the FORCE option on the new server.
Post #738301
Posted Monday, June 22, 2009 1:05 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, August 21, 2014 12:08 PM
Points: 1,414, Visits: 4,540
SP2 and later has been pretty good in that everything on both nodes was updated, but i'm still paranoid and like to failover all instances to each node and run the update and make sure everything on each node is updated

https://plus.google.com/100125998302068852885/posts?hl=en
http://twitter.com/alent1234
x-box live gamertag: i am null
[url=http://live.xbox.com/en-US/MyXbox/Profile[/url]
Post #739681
Posted Tuesday, June 23, 2009 2:56 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, June 26, 2014 9:49 AM
Points: 2, Visits: 344
I wanted to test out these steps on a test server first. Unfortunately my test server is SQL 2008 Standard Edition non-clustered. When I attempted to alter the resource database specifically the log file I encountered the following error:

To use ALTER DATABASE, the database must be in a writable state in which a check
point can be executed.
Post #740568
Posted Wednesday, June 24, 2009 1:42 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 4:34 AM
Points: 425, Visits: 549
This article is meant for SQL 2005 in a clustered environment. You probably don't need do these steps when you have a non-clustered environment. I haven't tested the method voor SQL 2008 either.

Post #740823
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse