Share via

Incremental Servicing Model

  • Article

The SQL Server team has moved away from the current priority-driven hotfix release model to a scheduled delivery model, called Incremental Servicing Model, designed to ensure that high quality fixes are delivered within an acceptable amount of time and on a predictable schedule.

 

The Incremental Servicing Model includes two ways to get fixes.

 

  • On-Demand and Critical-on-Demand: this method is used for problems that are impacting customers' applications and can't be addressed with work-arounds. On-Demand Hotfixes will be delivered as quickly as possible, by a date that the customer and Microsoft both agree to.

    The hotfix can be requested by any customer, regardless of their support offering, as long as it meets the criteria for the request.

 

  • Cumulative updates: these fixes will include all On-Demand Hotfixes that have been released leading up to the delivery of the cumulative update, as well as fixes created for less critical problems that don't meet the urgency requirements of the On-Demand Hotfixes.

Cumulative updates will be delivered every 2 months.

The hotfix can be requested by any customer, regardless of their support offering.

 

A GDR instead addresses an issue that has a broad customer impact, that has security implications, or that has both and will be released through the download center. A GDR is also released through Microsoft Update, through Windows Update, or through both.

 

 

For more information:

An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems

https://support.microsoft.com/default.aspx/kb/935897/en-us

 

- Beatrice Nicolini -

Comments

  • Anonymous
    January 01, 2003
    Yesterday, Francois Ajenstat, Microsoft 's director of SQL Server marketing, announced that Microsoft

  • Anonymous
    January 01, 2003
    Microsoft introduced an Incremental Servicing Model (ISM) is available from the SQL Server team to deliver

  • Anonymous
    January 01, 2003
    As you might (or might not?) know, since SQL Server 2005 the SQL Server team has moved away from the