Yep. I am in this boat. We have 7 dbs still in SQL 2000, 5 of which will be moved to 2008R2 next week. We still have a small amount in SQL2005 and a few of these we have upgrade plans for this year and a few more next year. We don't have SQL2012 yet here at all except for a sandbox play server. As far as home grown dbs why should we upgrade to SQL2012 now, might as well wait till SP1 comes out for SQL2014... as far as purchase apps our hands are tied to what is certified and when we decide to have a project, have the $$ and manhours to upgrade. We have over 300 prod dbs here now with 500 more in the next 2 years. As I have told my boss, if we did absolutely nothing except upgrade dbs to SQL2014 beginning today we would never have them all upgrade by the time the next version comes out. I thought Microsoft said each new version would be 3 years apart.... From my notes SQL2012 came out in May 2012, and SQL2014 came out in April.... that isn't three years! Our one store facing SQL Server had 50 databases on it and we began the upgrade project of moving/upgrading or replacing the 50 dbs from SQL2000 on it in Nov 2011 and will complete it next week. When you are dealing with a 24X7 highly avail. system that is critical to the business it isn't easy or quick to upgrade. We basically took each app/database one at a time and went through DEV, TEST and PQA and then Prod. The easiest ones first and the last group the most difficult.

I have been telling everyone that this over 2 year upgrade project took us from two versions old to today of now being two versions old. Kind of sad when you think about it in those terms.