THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | Join | Help

Home

Blogs

Downloads

Opml

Andy Leonard

Andy Leonard is CSO of Linchpin People and SQLPeople, an SSIS Trainer, Consultant, and developer; SQL Server database and data warehouse developer, community mentor, engineer, and farmer. He is a co-author of SQL Server MVP Deep Dives. His background includes web application architecture and development, VB, and ASP. Andy loves the SQL Server Community!

SQL Server 2005 SP4

Steve Jones (Blog - @way0utwest) shares he found a post confirming Microsoft's intention to deliver a Service Pack 4 for SQL Server 2005! Cool. Thanks for responding to the community, Microsoft.

When SQL Server 2005 was released, the community told Microsoft 5 years was too long to wait for a new release of SQL Server. Since they released SQL Server 2008 - less than three years after the release of SQL Server 2005 - the community has repeatedly communicated this was too soon.

I think both are accurate: for some folks, three years is too soon. For others, five years is too long.

Which describes you?

:{> Andy

Published Monday, February 15, 2010 8:00 AM by andyleonard

Filed under: SQL Server, Support

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

Eric Wisdahl said:

4 years? Just joking.

I think that with releases approximately 3 years apart it becomes more feasible for companies and individuals to "skip" a generation if they are the type that likes slower release cycles (i.e. 5 year life cycles). If you or your company are more into learning the latest technologies and utilizing the full power of these emerging technologies, then the 3 year life cycle is probably more to your liking. Personally, I like the 3 year cycle. But then, I also enjoy spending some of my free time reading sql tech books... so perhaps I'm not the best person to ask :-)

February 15, 2010 9:00 AM

Tracy Hamlin said:

I agree - Some feel 3 years is too soon and 5 years is too long. So let's go with 4 years!

Actually, my preference would be for Microsoft to have a clear picture of the improvements and updates it wants to make for the next release, project a time frame in which they can make the updates, then release when it's ready. I would much rather have a well-tested, stable release we can count on then just pushing out whatever they have (or may not have ready) on a certain time frame.

February 19, 2010 10:52 AM