July 12, 2009 at 12:09 am
Hi All,
Can you provide step -by-step procedure for service pack upgradation?(on sql 2005 server)
If possible,can u attach the screenshot for more clarifiction..
It will helps a lot for me:)
Please sahre your experiences on this event...
Waiting for help...
July 12, 2009 at 12:41 am
Is it clustered SQL Server or Stand alone SQL Server?
If it is Stand alone SQL Server, Installing Service Pack is pretty straight forward:
1.Down load and Read the read me file of the Service pack you want to install.
2.Backup all the databases, script the logins, jobs and save them in a safe location.
3.Do not stop any SQL services.Service pack installation will take care of that.
4.Start and follow the service pack install wizard steps.
5.At the end it will ask for a reboot. Because we did not stop any services at the start of the Installation.
Note: Before applying Service pack to a production server, Test it in a Test server, document the steps and apply for the development and QA servers and then finally apply for the production box
thanks
July 13, 2009 at 7:06 am
Also be aware that backing out a Service Pack pre-SQL Server 2008 is not a simple matter; you have to uninstall and reinstall SQL Server!
Regards
Lempster
July 13, 2009 at 10:44 am
Just so we can discuss this with clear terminology. there is no such word as upgradation, and a service pack isn't an upgrade. It's an application of a patch to the server.
What level are you going from to what level on the server? Is this an RTM, base version of SQL Server 2005? What service pack are you applying?
The basic steps are listed above from rambill4. Download, read the instructions, and it's generally an install like any other sofware. Make sure you have backups, and time to reinstall SQL Server if there are issues.
You ought to have tested this on a test server, and WITH YOUR application to be sure that a change won't break anything.
July 14, 2009 at 10:57 pm
Hello All,
Thanks for your all replys..:)
my server is 2005 server enterprise edition(not cluster) and current sp is sp2.
Kindly sugget me in sp patching for this server.
Thanks in Advance:-)
July 15, 2009 at 3:12 am
The replies you've been given so far plus the Release Notes for the Service Pack should be all you need to carry out a successful install of SP2. No one is going to post step-by-step instructions and/or screenshots - you need to do your own research.
January 6, 2010 at 9:50 am
How is this installation of patches is different for cluster from a standalone.
Thanks
Ali
January 6, 2010 at 10:02 am
Ali_SQLDBA (1/6/2010)
How is this installation of patches is different for cluster from a standalone.Thanks
Ali
Major difference being the downtime associated with applying patches on a Standalone server.
Thanks..
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
January 6, 2010 at 10:03 am
Ali_SQLDBA (1/6/2010)
How is this installation of patches is different for cluster from a standalone.
There's not too much difference; Make sure you do the install from the Active node, the install wizard will detect that you have a clustered instance (or instances) and will prompt you to select the instance(s) to be patched. The install process will patch BOTH nodes (assuming a 2-node cluster) so you only need to do it once.
You'll need to reboot each node after the install.
The readme files for each Service Pack usually contain a section with specific instructions or points to note when installing on a Failover Clustered Instance.
Lempster
January 6, 2010 at 10:54 am
My cluster is a AA cluster. So, I need to install on both nodes then. correct?
January 6, 2010 at 11:25 am
Ali_SQLDBA (1/6/2010)
My cluster is a AA cluster. So, I need to install on both nodes then. correct?
If you failover so that all your instances are running on one node then no, you'll still only need to install on one node. After the install and reboot you can then failover as necessary so that you have the correct split of instances between nodes.
Of course, if this is a Production cluster then you should be doing all of this in a maintenance window.
January 6, 2010 at 11:44 am
Yes Sir!! got it. I will work on it.
Thank you very much.:-)
January 6, 2010 at 11:52 am
Ali_SQLDBA (1/6/2010)
My cluster is a AA cluster. So, I need to install on both nodes then. correct?
If you only have single instances on both the Active nodes then you only need to apply the Service Pack on any one of the Active node. The changes will be copied over to the other node, but you will be required to reboot the nodes for the change to complete.
Thanks..
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
January 6, 2010 at 1:33 pm
If you have any non-cluster aware components installed, you have to run the service pack on each node where they are installed.
For instance, SSIS and SSRS will not be updated on the other nodes - and prior to SP3 (I think), the client tools also would not be updated.
The service pack will identify all components on that node that need to be updated and allow you to update them if needed.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
January 7, 2010 at 3:13 pm
Ali_SQLDBA (1/6/2010)
My cluster is a AA cluster. So, I need to install on both nodes then. correct?
Well, I don't like to open a can of worms, but there is no such thing as an AA SQL cluster.
An SQL cluster is always AP.
Viewing 15 posts - 1 through 15 (of 22 total)
You must be logged in to reply to this topic. Login to reply