exchange and database

Exchange 2000 mail server, backup, maintenance, problems and troubleshooting. AD, Forests, trees, etc


exchange and database

Postby veenabose » Fri Apr 10, 2009 2:28 pm

Originally, the next version of Exchange was supposed to move away from the Jet store to a new SQL database. Jet has been a popular database store and is also used for DHCP, WINS and Active Directory itself. However, unlike SQL, it has been less than a great solution for a large database such as Exchange.
Exchange is infamous for its database problems. Anyone who has ever had to migrate all the information using Exmerge because of a database problem knows what I'm taking about. A single corrupt item in Exchange can bring a whole server down. I've seen it happen.
On the other hand, SQL has always been Microsoft's most solid product. Unlike Exchange, it hasn't changed its core for years. It didn't have to. A lot of features were added but there was no real reason for changing the basic mechanisms. Customers were happy, the server functioned well under all kinds of conditions and proved as fast and as stable as the competitor's offerings.
After much grumbling, Microsoft decided on making all of its future products SQL instead of jet-based. The first of these was Sharepoint which successfully migrated from an Exchange like database to a SQL one. However, the Jet database is much more flexible than the SQL one. SQL has n-dimensional type tables, making information easy to find. Exchange, on the other hand, like Active Directory, has objects, placed in a tree structure that can vary.
This has caused Sharepoint to lose some minor features in the migration process which was not a big deal, seeing as the product wasn't as widely adopted yet as Exchange is.
To bridge the gap, the new SQL version, now dubbed SQL 2005, is supposed to bring about an unstructured database type. E12, however, will not use this type of database. Though a version of Exchange actually ran for a while on SQL in Microsoft's labs, this will have to wait for the next version of Exchange.
Microsoft executives, remembering the Exchange 5.5 to Exchange 2000 migration fiasco, decided not to burden Exchange administrators with having to change their architecture once again while user experience remained the same for most Exchange users, since the 5.5 version.
Instead, Exchange will remain essentially the same, yet a more mature and well-rounded environment.
Posts: 1
Joined: Fri Apr 10, 2009 2:01 pm
Location: hyderabad

Re: exchange and database

Postby nedved31 » Tue Sep 06, 2011 3:13 pm

For working out troubles with edb files you can use [url=]edb recovery[/url]. It has easy to use interface for any users, working under any version of Windows OS. The program can work with corrupted or lost .edb files.
Posts: 1
Joined: Tue Sep 06, 2011 3:11 pm

Return to Exchange & Active Directory

Who is online

Users browsing this forum: No registered users and 1 guest