Applying SP/Cumaltive update Package for SQL Server 2005

Question

Applying SP/Cumaltive update Package for SQL Server 2005

kokila-416295

Say Hey Kid

Points: 663
More actions
December 17, 2008 at 7:40 pm

#127614

Dear All,
I have few doubts about applying service pack/hotfix package for SQL Servers.
1.Microsoft recommends testing SP/ Hotfix in test environment before applying it to production server. Doubt 1: what it means exactly? Whether the test server should match the exactly configuration as production server (in configuration/User database wise).
2.Doubt 2: When we have to apply hot fix/cumulative update package? In some articles it is mentioned not to apply hot fix until we face problems mentioned in the KB articles of particular hot fix. Can I say my sql server 2005 instance is updated up to date if I apply sp2 ( Even Cumulative update package 11 also release three days before)
Need your valuable inputs
Regards
Kokila K

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply

HanShi SSC-Dedicated Points: 33507 More actions · Answer 1

1. You need to test updates/service packs/hotfix on a test environment. The best scenario is when this test environment matches the production environment. This includes the SQL instance (incl. databases) as well as the hardware. Every single part could create a problem related to the update. By having an identical test environment, you can exclude 99,999% of possible failures in the production environment.

2. For your information: SP3 is released and available for download.

There is a difference in how MS is testing a hotfix/Service Pack/Cumulitive Update. A SP is tested more intensive before release compared to a CU. It depends on the availability of your testing capabilities (time & environment) if you will apply a CU. Of course: if you experience problems that are solved by a specified CU or hotfix, you should apply this CU/hotfix.

Our company rule: Apply latest SP and CU (after testing:P). Only apply a hotfix when solving a specific problem.

** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

Jonathan Kehayias One Orange Chip Points: 26778 More actions · Answer 2

Microsoft recommends that you not apply a cumulative update unless it is specifically addressing a problem you are having. The reason for this is that CU's don't get the same level of regression tests that a SP will. That being said, CU10 has security rollups included in it that should make it pertinent to apply on any SQL Server. However, SP3 was released this week by Microsoft, but it does not contain the fixes that were in CU10 or CU11 for SP2. These will be included in SP3 CU1 which is due out in a few days.

You should definitely test the updates in a similar environment to your production environment, but it doesn't have to be identical. For example, I have 20 production servers, but I only have 3 development servers, but one of my development servers is x86 and one is x64 so I can apply changes to both and know how it will effect both in production. I don't have a dedicated development environment for each of my production servers. To do so would be a waste of resources and very costly.

If you don't have a pressing need, I would install SP3 and then the CU1 for it at this point.