First leaked in 2000, Microsoft still can't decide what the story is around moving Exchange to SQL Server.  It's on, it's off, it's committed, it's not.  And for sure, it's a point where Microsoft's spokespeople are particularly defensive:

"As we plan the next version of Exchange [currently code-named Exchange 14], it may be that the biggest breakthrough we can make for storage management is to switch to the SQL data store. We'll probably know that in about six months' time," [Terry Myerson] said.
Apparently, despite the reasons that Paul Flessner and others stated to do the move in the first place, now the spin is that it's not particularly urgent:
Dave Thompson, the corporate vice president of Microsoft's Exchange Server product group, told eWEEK that the team had decided to stay with the Jet engine in Exchange 2007 based on customer feedback around scalability, programmability and availability.
Julie Farris from Scalix chimes in with the reality check:
...claim that the underlying architecture of Exchange suffers from more than its fair share of reliability and security problems, the fundamental causes of which have not been addressed in Exchange 2007.

The Exchange message store, based on the Jet database, is prone to corruptions and is difficult to manage and maintain, she said, adding, "this is a long-standing, known problem, and plans to replace the Exchange message store have been iteratively postponed."
It feels to me like this article could have been written over five years ago -- how little has changed.

Link: eWeek: Exchange Data Store Change Still in the Cards >  (Via Peter O'Kelly)

Post a Comment