• subscribe
June 19, 2007 12:00 AM

Leapfrogging to Katmai

SQL Server Pro
InstantDoc ID #96348

What percentage of SQL Server customers would you guess have already migrated to Microsoft SQL Server 2005 from older versions such as SQL Server 2000? I hadn’t thought about this particular number much in recent months, but the release of the first SQL Server 2008 (code-named Katmai) Community Technology Preview (CTP) at TechEd got me thinking about SQL Server 2005's adoption rates. I’ve been chatting with several people at Microsoft and many other folks who are plugged into the SQL Server community in various ways. Some people have guessed that SQL Server 2005 adoption is currently in the 15–30 percent range, although most people guessed it's in about the 20–25 percent range. The results don’t surprise me too much, although my guess is in the upper end of the range, with "guess" being the operative word. My survey wasn’t a formal, moderated study, and the people I polled hadn't done formal surveys of their own. But as I said, the people I spoke with are pretty plugged into the SQL Server community, so I trust their estimates.

I wonder what impact SQL Server 2008 release plans will have on the large number of customers who haven't yet migrated to SQL Server 2005. Typically, I would expect that we’d soon be entering the sweet spot for upgrades to SQL Server 2005. However, Katmai is now only about 18 months away, assuming that Microsoft ships it by the end of 2008 as promised. I assume that customers with plans to upgrade in the next two or three months will probably stick to with that plan, but what if you didn’t plan to upgrade to SQL Server 2005 for another 6–9 months? That would put you just 9–12 months away from the SQL Server 2008's estimated release date.

Sure, you probably want to migrate to a newer version of SQL Server, but the fact that you’d be upgrading to SQL Server 2005 about two years after it was released suggests you’re more turtle than rabbit when it comes to upgrades. If you've lived without SQL Server 2005 for two or more years, could you wait a bit longer, jump straight to SQL Server 2008, and save a tremendous amount of time and cost by skipping an entire upgrade cycle? I suspect that many SQL Server customers will be tempted to explore that route. Of course, Microsoft will certainly want its license revenue, and you can’t blame the company. I would expect Microsoft to counter that route with various white papers to help evangelize the benefits of migrating to SQL Server 2005, and I wouldn’t be surprised to see Microsoft being aggressive with discounts for its large customers to entice them to migrate to SQL Server 2005 sooner.

I’m curious about what you expect to do if you haven't yet migrated to SQL Server 2005. Will you wait another 18 months and leapfrog straight to Katmai?



ARTICLE TOOLS

Comments
  • Maurice
    5 years ago
    Nov 23, 2007

    We are application providers, and we are almost at the end of certifying our applications for SQL2005. We are also going to drop support for SQL 7 and SQL2000 at the mid 2008 year. Our customers may buys actually SQL2008 licences and use SQL2005, so we could plan support for both platforms, which always make things a bit more compicated for us. Two sets of servers for testing are required and double that again for x86 and x64 platforms. We can't ask our customers to upgrade again from SQL2005 to SQL2008 because of the short time in between. The best we can do it to tell them to wait and buy SQL2008, which could slow down the move to SQL2005, what we don't want either. What is boring about programming in bi-platform support, is that we can't use new features easily unless we introduce extra programming. Programming without the new features, and programming for the new ones is expensive unless the advantage is huge for end results.

  • J.
    5 years ago
    Jul 01, 2007

    None of our customers have upgraded to 2005. Only entirely new webservers are now being rolled out with 2005; all production machines are still on 2000 and I expect those to stay that way till 2009.

  • Daniel
    5 years ago
    Jun 28, 2007

    Eighteen months is a long time to wait when it comes to a technology upgrade such as this. For those of us with really large databases, the administrative tools in SQL2005 compared to SQL2000 is just about enough to justify going to SQL2005. I view the upgrade from SQL2000 to SQL2005 a major jump in the product technically. Actually we are leaning more toward skipping SQL2008, because we have not seen functionality in it to warrant the wait.

    Dan Poff
    Director DBA & SAP Basis
    Kindred Healthcare Inc.

  • Desperado
    5 years ago
    Jun 22, 2007

    We just retired our last SQL Server 7.0 out of our 65+ SQL Server instances farm. We are jsut started our SQL2005 migration - about 10% done. Even if SQL 2008 comes out on target, I do not foresee a move to it until at the very least Fall 2009.
    We will not be able to move out 2000 until such time as all our 3rd party suppliers have move on to more recent RDBMS. And THAT may very well lead us into 2000's end of its lifecycle.

  • Rudy
    5 years ago
    Jun 22, 2007

    We also have migrated abount 15% to SQL 2005.
    Most of the time we are waiting for the application that connects to its database to give a go for the 2005 compatibility.

You must log on before posting a comment.

Are you a new visitor? Register Here