In response to customer feedback, SQL Server team has revised the mechanism to deliver hotfixes on reported bugs with a new model called Incremental Servicing Model (ISM). The objective is to deliver high quality fixes within an acceptable amount of time and on a predictable schedule.
We have moved away from current “priority driven” hotfix release model to a scheduled delivery model in which a customer can get a hotfix to service their most critical situations with a short turn-around time or a fix that has undergone higher levels of testing is released on a scheduled basis. As a result we created the two delivery mechanisms outlined below:
1) An On-Demand Hotfix request:
a. The issue must meet the criteria for this request (including a lack of a viable work-around, critical business impact, etc.)
b. May be requested by any customer regardless of their support offering as long as it met the above bar.
c. Is released on or before a mutually agreed date based on customer’s need
d. This hotfix build could contain one or more fixes.
2) Cumulative Update:
a. May be requested by any customer regardless of their support offering.
b. Is released every 2 months.
c. Is a Cumulative Update build containing:
1. All previous on-demand hotfixes to-date
2. Fixes for issues that meet hotfix acceptance criteria which considers the work-around availability, customer impact, reproducibility, complexity of code needing to be changed, etc.
While we are rolling out this revised model, there are several other projects are being done concurrently to focus on improving the quality of SQL Server at ship time to reduce the need for hotfixes of this nature
По-видимому, то огромное количество проблем, которые возникали у потребителей после установки последних
In benefit of our readers, I've taken the liberty and asked SQL localization team to translate Mr. Gladchenko's comments as following:
Changes in approach to releasing cumulative patches for SQL Server
It seems that the enormous amount of problems users experienced after setting up the latest SPs and patches forced the SQL Release team to announce changes in their concepts of development, testing and releasing. This could be considered as a good news, especially after “wonders” of the SP2 and a flood of patches and unsuccessful fixes :) As Keith Fang announced in the Microsoft SQL Server Release Services blog, the mechanism of releasing patches and SPs will be linked to milestones instead of releasing them they as soon as they are ready (like it used to be for the operating systems and office applications), with the release period of two months. In other words, in the new Incremental Servicing Model new patches will be released by a certain date, i.e. the process of development and testing will be more predictable.
In addition to the mass-model called "Cumulative Update", the individual model "On-Demand Hotfix request" remains in place. It considers that a client will receive data about how the patches have been prepared and make a decision on whether or not to have them installed.
In addition to known QFE patches there is going to be a new ones – GDR. The main difference is that their usage is really important, and they are rather critical. The most confusing part is the new numbering of the patches: for instance, for the last GDRs the range was 3049-3149, while the QFE range is 3150 and above… With this – not that complicated – way it was possible to set up only selected GDRs or install a QFE, which installs everything.
These and the other changes [made by the SQL Team] should result in increased quality and reduced frequency of the patches. As we all saw, the previous model didn’t met requirements for such complex and complicated product as SQL Server 2005.
Alexander, please correct any mistake we may have made. Thanks.
GDR stands for General Distribution Release and it is not a new delivery vehical in ISM. Prior to the recent SQL Server 2005 SP2 GDRs, the last GDR released on SQL is the fix for Slammer worm.
It is correct that we separate the version numbers of GDR and Hotfix releases so the Microsoft Update (MU)applies the appropriate version of GDR based on what has been installed on customer's machines. For example, MU will install GDR if it finds the currently installed version is below 3150, on the other hand, if currently installed version is above 3150, MU will install the Hotfix package which contains the same fix in GDR package.
The Incremental Servicing Model is also described in the following KB Article:
Probabilmente a causa dei problemi avuti con il Service Pack 2, la Microsoft ha annunciato di aver effettuato
The SQL Server team has released a new service model called: Incremental Servicing Model. You can get