So here’s the reality. Today we’re running Community Server 2008 sp1 and the data is built and stored in SQL 2005. As a result of this migration we’ve lost some attachments, images, and for the decorator in me, blog skins that work. Not the greatest migration that I would have hoped for. So I look around at other blogging platforms and the options I have to move the data, I realize that I’m not sure where to turn. The content is in SQL 2005. WordPress and Typepad run in MySQL. Quite frankly, unless things change, I’m not sure I have the braincells left to handle another database engine, especially one that I’d only use for the blogging platform.
So the article above that urges Microsoft to make a break with the past showcases to me how much the pundits don’t understand that when it comes to data and business, one does not rip out and replace lightly. It’s the reason entire firms are not ripping out XP and migrating to Vista. It’s the reason firms are still on Office 2003. One does not migrate lightly. One HAS to ensure that once they get on migrated platform that the business is not adversely impact.
If this blog site was a true business and my “business” was impacted to the degree this migration impacted this platform I’d be concerned about the productivity and efficiency impact of my firm.
Bottom line, migrations suck. Upgrades are never without risk. And for all that we’d love to rip out and start over, get real. Real world doesn’t work like that. Once cannot rip out without major impact.