SQL Server Release Services - Cumulative Update or frequent Service pack releases, which one you favour?
Here is the hot news, SQL Server Global Release Services (GRS) has revised their schedule of releasing Service Packs for SQL Server product by stating 'changed approach to Service Packs'. Now the big question how far you can stretch in deploying these service pack releases within your Enterprise database platform to deploy frequent service pack releases.
What has been referred on their blog is:
With our recent SP3 announcement we will be expanding the Incremental Servicing Model to now include Service Packs and we will pursue the following objectives:
· Smaller Service Packs which will be easier to deploy
· Higher quality of Service Pack releases due to reduced change introduced
· Predictable Service Pack scheduling to allow for better customer test scheduling and deployment planning.
If you are confused or not sure about Release concepts then refer to ISM-Concepts article. The four important factors for every release are:
· GDRs (General Distribution Releases)
· Hotfixes
· CU (Cumulative Update)
· Services Packs
Is it feasible for you to deploy the SP release within every 6 month period?
What is the current approach you have on Cumulative Update releases?
What is your high availability figure, can you achieve 99.999%?
Practically it is not possible to deploy the service pack release in every 6 months and moreover the practice should be to check whether that SP release is applicable to your environment or not by referring to the README.HTML file. Going further you can even test the pack by installing within your Test platform with a rigorous testing from the application to ensure it will not break out any layers of availability.
I have seen that release of service pack deployment is more wanted for the Customers that are satisfied with Service Pack release rather than Cumulative Updates, but think about availability and arranged downtime to apply these service packs. It may be good that you need not restart the server after applying, but to restart SQL Server services. Also it will be more feasible if Microsoft release team can provide with uninstall method with 'no strings' attached.