| Author |
Topic |
|
edimen
Starting Member
12 Posts |
 Posted - 2010-04-16 : 13:24:43
|
| Hello,I am looking for suggestions on best and safest way to apply SQL 2005 service packs and other necessary updates. The current installation version is 9.0.1399.06.My questions are:1. What is the safe level of the service pack to install?2. Can we start with SP3, or have to start with SP1, etc?3. Can SQL 2005 updates be downloaded using Windows update? If not, is there any way to get new ones automatically?Thanks! |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-04-16 : 13:38:22
|
| Depends how mission-critical your database & application are.We take the viewpoint that we will not install a Service pack without a full regression test, and that is a pretty major commitment from our part.What if the Service Pack breaks your application? Will you be able to fix it promptly, or will you run the risk that users are alienated against your application, or worse: against your company?1) All as safe as each other. Waiting a few weeks in case Microsoft issue an emergency recall and a "Service pack 'A' version" is prudent (this has happened in recent memory). For SQL 2005 the most recent Service Pack for SQL2005 is SP3 released in DEC 2008, but there are "fixes to this" (i.e. Cumulative Updates) released as recently as Feb 2010.2) You can just download the latest Service Pack, you do not have to install 1 then 2 then 3 ....3) Personally, because we perform a full regression test, I would not want SQL to update automatically under any circumstances; people with less mission-critical databases might take a different view, of course. |
 |
|
|
edimen
Starting Member
12 Posts |
Posted - 2010-04-16 : 13:56:35
|
| Thanks so much for the answers!Would you recommend applying the latest post-SP3 Cumulative Update package (after testing) as well?What's the best way to apply CUs - install only if any fixes apply, or install all in a test environment, and if nothing breaks, apply in production?Also, if additional SQL components (like Reporting Services) are added after the SP3/CUs are installed, do you need to reapply SPs/CUs?Thanks!! |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2010-04-16 : 15:04:07
|
| "Would you recommend applying the latest post-SP3 Cumulative Update package (after testing) as well?"In general terms NOT unless you encounter a problem specifically fixed by the Cumulative update. My understanding is that cumulative updates are not as well tested as Service Packs.However, in SQL2008 MS seems to be releasing a lot more CU's, and maybe they are expecting people to install them with less rigorous conditions. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-04-17 : 07:59:57
|
| Very useful info, thanks Tara. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
edimen
Starting Member
12 Posts |
Posted - 2010-04-19 : 11:46:35
|
| Tara - really appreciate the information, thanks!Is that October hotfix the same as one of the SP3 Cumulative Update packages? It looks like SP3 CU5 brings you up to build 4230; SP3 CU6 makes it build 4266, and that's higher then 4262 you mentioned. Also, there is a CU7 with build version 4273 - should that be OK to install?Since they are called 'cumulative' sounds like CU 7 will include CU1-6 as well?Finally, I've been trying to figure out how to best get notified about new SQL updates - is this the best site to use? http://blogs.msdn.com/sqlreleaseservices/default.aspxThanks again! |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2010-04-19 : 12:45:13
|
| Go with CU7. I think there may even be newer one out there. I just returned from maternity leave today, so I'm not yet up to date on everything.Build 4262 is a cumulative update package but isn't labeled CUn like the others. The October hotfix had two packages released. The first was just to fix the security vulnerability in SP3, but it did not include any other post-SP3 fixes. The second one was the fix for the security vulnerability plus all of the other fixes in the other CUs. 4262 is the cumulative one. I'm not sure of the best place for updates, but that does look promising. We receive emails directly from Microsoft in advance of the public, but we are a Premier customer so your mileage may vary.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2010-04-20 : 03:25:08
|
| List of versions here:http://www.sqlteam.com/article/sql-server-versions |
|
|
|
edimen
Starting Member
12 Posts |
Posted - 2010-04-20 : 17:45:33
|
Thanks for your help guys! Congratulations on the new baby, Tara  ! Finally installed SP3 and CU7 with no problems, except for a persistent 'information' error 17890 (A significant part of sql server process memory has been paged out) that according to some sources is normal on a completely idle SQL server... but I guess that's a topic for another post. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
edimen
Starting Member
12 Posts |
Posted - 2010-04-23 : 11:03:37
|
| I have enabled the 'Lock Pages in Memory' right for the SQL service account, but still gettings the same 17890 errors...Thanks! |
|
|
|
|
Applying SQL2005 service packs and patches