April 3, 2010 at 1:23 am
Hello,
On one of my MSSQL 2005 ( 64 Bit) Edition -- Current build is -- 9.0.3353
The MSSQL Database engine is going to be upgraded with SP 3.0 .
a) Please let me know what pre installations steps needs to be followed.
b) Also is it possible to directly update the above mentioned build to SP 3.
c) What would be the risk factor involved if the patch installation gets corrupted
Thanks
April 3, 2010 at 2:51 pm
Hi,
Your build is 9.0.3353 - Cumulative update package 13 (CU13) for SQL Server 2005 Service Pack 2.
You can upgrade the MSSQL Database engine to SP3 directly. In fact, a service pack contains all the cumulative updates released earlier. You don’t have to do the CUs one by one.
The main/important pre – installation steps depends on whether the instance is in a clustered environment or not.
If it is in a clustered environment:
1.Make sure the ‘Task Scheduler’ service on all the nodes are enabled and started.
2.Ensure no RDP sessions are there on other nodes while installation. You can use ‘Terminal Manger’ for that.
3. At end, please check the ‘View Summary’ log for the version changes and errors if any.
On both clustered and Standalone servers’ cases:
1.Make sure you have administrative rights on the node and ‘sysadmin’ rights on SQL instance.
2.Enough free space on C: drive to do an installation.
Do take a backup of all the databases including the system databases before proceeding with installation.
If the instance is SQL Express, then download separate installation file from Microsoft. Service pack for express is different from other editions.
Find the list of bugs fixed in SQL server 2005 SP3.
http://support.microsoft.com/?kbid=955706
Cheers
John
April 3, 2010 at 2:59 pm
Also, When you upgrade instances of SQL Server 2005 in a merge replication topology or in a transactional replication topology with updating Subscribers, you must upgrade the instances in the following order:
1.Distributor
2.Publisher
3.Subscribers
John
April 3, 2010 at 5:15 pm
9.0.3353 appears to be SP2 + CU16 + some individual hotfix?
Are you applying CUs simply because they are being released or because you have hit an issue fixed in CU16? there is no need to apply CUs unless you are experiencing the issues they address.
SP3 only contained the SP2 CUs up to CU9. SP3 CU1 contained SP2 CU10 and 11 so you would want to apply that at least. after that it depends what hotfixes you wanted due to issues encountered. If none stop at SP3 + CU1
http://www.sqlservercentral.com/articles/Administration/2960/
---------------------------------------------------------------------
April 3, 2010 at 5:56 pm
Thanks George.
A question from my side is that if SP3 CU1 has SP2 CU10 and CU11, then how can we add the SP2 CU12 to CU17 after the SP3 installation. Is there any other release in SP3 which has SP2 CUs from 12-17
Thanks.
John
April 4, 2010 at 3:09 am
Thanks a lot for replying.
In my Environment there is no high availability solution implemented.
In SP3 + CU1 do we get any benefits from Database administraion point of view ( kind of performance enhancements ) apart from the bugs which are fixed ? .
April 4, 2010 at 3:47 am
Hi Nikhil,
You will have to do a bit reading about the FIXES in SQL Server 2005 SP3 CU1.
Certain fixes are performance enhancements, like below:
50003965956686 FIX: When you run a query that contains a JOIN operation in SQL Server 2005, and the ON clause of the JOIN operator contains a LIKE predicate, the query runs slower than in SQL Server 2000
50003970958500 FIX: MDX queries that use the EXCEPT function in the WHERE clause run much slower after you install a hotfix or a cumulative update whose version is later than the version of Cumulative Update 4 for SQL Server 2005 SP2
50003955960543 FIX: The x64 version of SQL Server 2005 may crash when you are performing backup
Thanks
John
April 4, 2010 at 4:38 am
bigM (4/3/2010)
Thanks George.A question from my side is that if SP3 CU1 has SP2 CU10 and CU11, then how can we add the SP2 CU12 to CU17 after the SP3 installation. Is there any other release in SP3 which has SP2 CUs from 12-17
Thanks.
you don't, you are on a different path from that point. There is no one to one relationship between post SP2 and post SP3 CUs. you need to identify any hotfixes that actually fix an issue you have and apply the CU that contains it. If you don't have any issues stop at CU1, but you have put yourself in a position of having to test more carefully in case the CUs changed some behaviour.
If you have stuck this long with post SP2 CUs and everything is stable I would be tempted to await SP4 (due out late this year), and don't apply any more CUs.
This is another reason not to apply CUs unless you have an issue that requires it be applied. Apply SPs when they come out, but not CUs.
---------------------------------------------------------------------
April 4, 2010 at 4:43 am
nikhil.verma (4/4/2010)
Thanks a lot for replying.In my Environment there is no high availability solution implemented.
In SP3 + CU1 do we get any benefits from Database administration point of view ( kind of performance enhancements ) apart from the bugs which are fixed ? .
unlikely, but because of the version you were previously on you should apply it.
As said before, only apply CUs if they address an issue you are facing, do not apply by default.
Having said that if you are on standard edition take a look at SP3 CU4, IIRC it allows use of lock pages in memory with 64bit which could help you.
apply and test in dev environment first though.
---------------------------------------------------------------------
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply