Contact Us     Newsroom     Resource Library     Home

 General Questions

 Supported Systems

 GOexchange vs. Microsoft Tools

 GOexchange vs. the Competition

 GOexchange used with Exchange Archive
   and High Availability Solutions


 Licensing

 Updates & Upgrades

 Support & Maintenance Program

 Installation

 Starting GOexchange

 Logging In

 Configuring GOexchange

 Operation

If you have specific questions that are not currently answered within the FAQs, please send an e-mail to L8support@lucid8.com and we will be happy to assist you.

Does Windows Disk Defragmenter or Diskeeper accomplish the same things GOexchange does?

No. The built in Windows defragmenter, Diskeeper and other third party disk defragmentation utilities accomplish totally different results then those achieved by GOexchange. 

First, it's important to understand that GOexchange is much more then a defragmentation tool. GOexchange works with expert knowledge and consistency at the database level. GOexchange can repair errors and warnings, fix minor inconsistencies, consolidate white space, rebuild the database itself, and ensure that group collaboration objects like mail, tasks, calendar and other items are optimized and in tact.

Disk based defragmentation tools focus on ensuring files are laid out across a disk in a contiguous fashion.  Doing so speeds up the operation of products because the files can be accessed in a more efficient manner.

In addition disk based defragmentation shouldn't be necessary on the drives containing the *.EDB and *.STM files  because Microsoft extends the Exchange databases in 16-MB chunks, therefore the Exchange databases are usually not fragmented enough to warrant a defragmentation of the file system itself. You can certainly run a disk defragmentation if you like, but you typically don't see a performance gain due to using the built in and or third party disk based defragmentation tools.

NOTE: At one point there was a bug in Exchange 2000 that would cause it to extend the database by only 1 MB at a time, and in that case the database would become very fragmented and a performance issue could result. However, that has been fixed since SP1. 



Home | Products | Support | Services | Partners | Purchase | Company | Resource Library

Success Stories | Testimonials | Newsroom | Contact Us | Site Map | Product Documentation
Copyright © 2009 Lucid8. All Rights Reserved.

privacy  |   legal  |   feedback