Last week, my press contacts at Microsoft told me about the company’s new Incremental Servicing Model for SQL Server, a new process for customers to receive scheduled SQL Server hotfix updates that is scheduled to launch April 16. The name and the brief description sure sounded intriguing. But, try as I might, I haven’t been able to get much in the way of real information about what this new initiative really means to customers. Honestly, that’s a bit weird. Typically, Microsoft releases a ton (a very precise journalism term that means a lot) of information about new customer-facing initiatives on its Web sites and blogs. And within a few days, dozens--if not hundreds--of talking heads just like me are sharing their incredibly insightful opinions on the topic. However, at about 9:30 p.m. Eastern time on Tuesday, April 10, when I Googled “Incremental Servicing Model,” I got just three hits.

I hate to rely too liberally on the “background” information that my Microsoft press contacts provide me, but since there’s not a lot of meat for me to chew on my own, here’s what Microsoft told me. The Incremental Servicing Model is a process that Microsoft developed in response to customer feedback. Presumably, when customers know that they are going to get an update, they can more effectively plan for (and minimize) downtime.

Currently, you can get hotfixes in bundles called Cumulative Updates, which include all the necessary fixes to date and are released every two months. The Incremental Servicing Model lets you opt in to receive automatic notifications when the newest Cumulative Updates become available.

For cases in which users encounter an urgent problem that doesn’t have a workaround, you’ll be able to download “On Demand” hotfixes. You’ll be able to sign up for the Incremental Servicing Model starting April 16. Look for the service’s availability at http://support.microsoft.com.

You can read the Microsoft blog on this topic, but with the limited information available from my Microsoft contact and this blog, I’m still a bit in dark. The blog does state that the hotfix Cumulative Updates will be released every two months and emphasizes that this program will not replace traditional service pack releases. But historically, hotfixes weren’t widely distributed, so at first glance it does seem like it will be hard to clearly define the difference between a service pack and an every-other-month Incremental Servicing Model release. I also have questions about testing the hotfixes and how to know when an Incremental Service Model update really needs to be applied to all of your enterprise servers and when it’s option, like a Saturday-night bath. I’m certainly looking forward to learning more about this intriguing model. I’m sure you are too.

Normally, I like to think my editorials are informative and make your life easier. This time around, how about a little help? Let me know if you’ve found better resources on the Incremental Servicing Model and I promise to share with other readers. You can post your information in the comments section at the bottom of this article page or send your news directly to me at brian@solidqualitylearning.com.

End of Article




You must log on before posting a comment.

If you don't have a username & password, please register now.

Reader Comments

no comment

micber

Article Rating 2 out of 5

Hi Brian, Found another article related to this new model, doesn't more info than you have already provided.

http://www.crn.com/software/198800822;jsessionid=GLA4XWVOGREZ0QSNDLRCKH0CJUNN2JVN

Thanks for bringing the latest to us.

Cheers

Jag Sandhu jag.sandhu@db.com

jagsandhu

Article Rating 4 out of 5

I just think that it's ridiculous that M$ is scared of service packs

instead of giving us 4,000 different patches for Windows XP; we should already have SP3, SP4, SP5

seriously

how long would it take to run windows update if we had more service packs? I'm tired of waiting for updates, sitting there scanning every file on my computer

SIMPLIFY Microsoft, SIMPLIFY ADP Uber Alles

-Aaron

akempfDOL

Article Rating 5 out of 5

Aaron, this has nothing to do with service packs. And Brian's article is not quite accurate.

Before the new model, hotfixes were delivered on a "one off" basis. The flow was something like this:

1. Customer calls with a issue 2. Issue is determined to be a bug with no workaround 3. Based on the priority of the issue, a fix is created within a certain timeframe 3. Hotfix is built 4. Hotfix is tested 5. Hotfix is released to the customer

The problem is when several hotfix requests come in at the same time. The ability to reliably deliver a fix on time decreases with each new issue in the system. In addition, the interaction between multiple fixes can cause new problems that could go undetected without thorough testing.

The cumulative update model was created to 1. increase our ability to deliver fixes on a set schedule and 2. increase the quality of the fixes we release. It is not a new service or a replacement for service packs.

Brian Welcker

bwelcker

Article Rating 3 out of 5

 
 

ADS BY GOOGLE