THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Andy Leonard

Andy Leonard is an author and engineer who enjoys building and automating data integration solutions. Andy is co-host of the Data Driven podcast. Andy is no longer updating this blog. His current blog is

SQL Server 2005 SP4

This blog has moved! You can find this content at the following new location:

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

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



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

Leave a Comment


This Blog



My Latest Book:

Community Awards

Friend of Red Gate

Contact Me


Privacy Statement