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 12»»

How to install SQL Server SP4 on a Cluster environment??? Expand / Collapse
Author
Message
Posted Thursday, March 17, 2011 6:49 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, September 18, 2013 8:21 AM
Points: 230, Visits: 411
I have SQL Server 2005 Enterprise edition. I need to install SQL Server SP4 to be installed which was released in Dec 2010. Now we have a Active\Passive node and i need some instructions on how to install SP4 on a Active\Passive node.
This is my first installation on a Cluster environment so please try to explain me in detail the steps required to update to SP4.
Thank you.
Post #1079609
Posted Thursday, March 17, 2011 7:53 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, September 18, 2013 8:21 AM
Points: 230, Visits: 411
any idea friends???
Post #1079653
Posted Thursday, March 17, 2011 9:57 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, September 26, 2014 3:36 AM
Points: 1,192, Visits: 698
1. ensure you have 3gb disk space free on the system drive of all nodes
2. ensure you are logged on with local admin privileges
*edit* and the account you are using to run the patch (normally your own) has logged onto all nodes previously to create a user profile.
3. take system database backups. I stop the SQL cluster resource copy the system database to a subfolder and restart the cluster resource in case everything goes bang. As copying the system DB from a subfolder is a lot less work than trying to restore system databases from backups using DAC.
4. rename sa account back to sa if it has been renamed KB955706
5. if the distribution db logs have been moved, put them back in the default location KB970892
6. you might need to install Visual Studio 2005 SP1 on all nodes first depending on what components you have installed. Some people say this is a prerequisite but I am not entirely sure.
7. Apply service pack on active node
*edit* there must be no one logged onto the passive node when the active node is being patched or the installer hangs.
8. Apply service pack on passive node
9. Restart each node of the cluster and test SQL works fine on all nodes using client application.
10. run backups of system databases and also run a tlog backup on each node to test SSIS.
11. check patch didn’t cause “Named Instances on Windows Cluster changed from Mixed Mode to Windows only after reboot randomly” http://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=480487

Further notes at http://social.technet.microsoft.com/wiki/contents/articles/microsoft-sql-server-2005-sp4-release-notes.aspx and http://download.microsoft.com/download/B/7/3/B73AFEF4-1A6C-42E6-B5A8-CBF990687A9E/ReadmeSQL2005SP4.htm

If there are problems consult “Failover Cluster Troubleshooting” http://msdn.microsoft.com/en-us/library/ms189117(v=SQL.90).aspx

Not that you would do it during a service pack but make sure the service account does not get changed on a cluster when the SQL resource is down or offline on any nodes. I have had this cause issues like SQL Agent only running on one node. http://msdn.microsoft.com/en-us/library/ms178061(SQL.90).aspx
Post #1079815
Posted Thursday, March 17, 2011 11:31 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, September 18, 2013 8:21 AM
Points: 230, Visits: 411
thank you. atleast this might help me at some point.
Post #1079902
Posted Thursday, March 17, 2011 12:04 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, August 8, 2012 6:26 AM
Points: 14, Visits: 114
Hi,

log shipping restore job got failed due to below error. i find that error from alert job. please assistance how to troubleshoot that.

The log shipping secondary database XXXXXXXDATA.XX_DB has restore threshold of 45 minutes and is out of sync. No restore was performed for 193 minutes. Restored latency is 6 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14421). The step failed.

and also i checked the log_shipping_monitor_secondary table on secondary server i got the error like restore failed due database in use .
Post #1079934
Posted Thursday, March 17, 2011 3:30 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 1:22 PM
Points: 5,872, Visits: 12,978
please don't hijack threads. start a new thread with your question if you want help.

nice answer on the SP application by the way. I would add ensure any server level triggers are disabled and take normal system db backups as well as a belt and braces approach. I highly recommend taking file copies of the system dbs before and after though, including mssqlsystemresource.


---------------------------------------------------------------------

Post #1080080
Posted Wednesday, May 4, 2011 6:37 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, September 17, 2014 8:56 AM
Points: 139, Visits: 385
Thanks. Those are good instructions but I have never had to install a SQL service pack manually on both cluster nodes (active then passive). I always run the SP on the active node and the SP takes care of the install on the passive node at the same time.

If it's a multi-instance cluster, you must move all SQL instances to one node and run the SP there.
Post #1103048
Posted Tuesday, October 18, 2011 8:44 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, December 3, 2012 7:43 AM
Points: 5, Visits: 53
Hello James,

I am going to apply the SP4 on our MSSQL 2005 clustered environment this weekend. I want to ask why do we need to apply the patch on the passive node ? I would have thought applying to the Active node would write to both underlying nodes but is it does as a precautionary step or is there something reason ? (I just want to understand what SQL is doing and not to question your step process) !
Post #1192156
Posted Tuesday, October 18, 2011 8:59 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:36 AM
Points: 6,423, Visits: 13,818
James_B (3/17/2011)
2. ensure you are logged on with local admin privileges

more importantly, the account you run the service pack under must have admin access to the sql server instance. If you removed builtin administrators from SQL Server then manually ensure the windows account you are installing as has been provisioned appropriately


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1192168
Posted Wednesday, October 19, 2011 8:11 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, September 26, 2014 4:00 AM
Points: 23, Visits: 114
Yeah, most of points above are correct. Some clarifications:-
SQL Server 2005 uses task scheduler service to install the patch on the remote node as well. SO you don't have to install the patch separately on the passive node.
Ensure that you verify the task scheduler service running on both the nodes.

Many times the remote task (SQL setup) would get created but it wont run on the passive node due to some issue. Check the task scheduler logs on the passive nodes to investigate further.
You can also test the task scheduler running fine by creating a task on the passive node and running it remotely.
Post #1192871
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse