Late last Friday, long after most people had gone home for the weekend, Microsoft SQL Server Release Services posted an blog that made my weekend. It was a short blog, but contained this bulleted item:

• SQL Server 2005 SP4. You overwhelmingly requested another servicing release for SQL Server 2005. Given your feedback Microsoft targets now such release in Q4/CY2010....

With over 1,000 votes for the Connect suggestion for SP4, Microsoft decided to listen and produce this Service Pack. The community made their feelings known, and it worked. I have no doubt that without the large number of votes that you entered, this Service Pack would not be coming. Thanks to all of you, and I hope that this is a decision that most of you support. If you haven't voted, I'd still go vote and let Microsoft know that we find Service Packs not only valuable, but invaluable ways to patch our database servers.

In addition to the announcement of SQL Server 2005 Service Pack 4, there also was the announcement of SQL Server 2008 Service Pack 2. That is slated to be released in Q3 of this year, so both of these patches are being delayed until near the end of the year. I would also anticipate SQL Server 2008 R2 Service Pack 1 to be released in Q4 of this year.

A few years back, the Release Services team had committed to a Service Pack schedule of SP1 6 months after the RTM, and then yearly Service Packs after that. No mention was made of the total number of SPs during the life-cycle of a product, which is slated to be 5 years in terms of mainstream support. In my mind we ought to have gotten SP4 by now, and should be expecting an SP5 when mainstream support for SQL Server 2005 ends. In that way we would have a roll-up of all patches for the life of a product.

I have the feeling that SP3 and SP4 for SQL Server 2008, as well as all future post SP2 service packs will require efforts on the part of the community. In the servicing model post, there was also this quote:

As a development organization we review customer issues and votes on a regular basis.

To me, this isn't the way Microsoft should provide support to their customers. A solid, reliable method of receiving patches should be available for customers who spend a significant amount of money on SQL Server. I suspect that we will need to submit and vote for Connect items over the life-cycle of SQL Server. I'll be sure that I keep doing so if you keep voting.

Steve Jones