Jeff, I appreciate you digging into stuff like that, it's why we need the early experimenters and the early adopters. I'd like to think that v.Next is always better/faster/stronger than v.Current, but there are exceptions and those exceptions can be a killer. We just had this conversation at work recently, one database left on 2008 that wasn't targeted to upgrade to 2012 and now a dependency has been discovered - can we just upgrade it? Sure! Odds are it doesn't use any deprecated feature, but we can't guarantee performance, it has to be tested. It would be nice to never have that worry about an upgrade!