Long live Jet!
Exchange 2010 continues to use ESE, its version of the Microsoft Jet database engine that is shared with other Microsoft products such as Access. Of course, ESE is very different than other Jet databases, because it has been highly optimized over the years for Exchange—a process that continues with the new schema introduced with Exchange 2010. Some are surprised that Microsoft persists with ESE as the platform for Exchange when they seem to have another perfectly good enterprise-class, high-performance database engine in SQL. On the surface, it’s an attractive notion to unify all database development activities into a common platform that Microsoft and third-party developers can support. Money would be saved on engineering, testing, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access