Article ID: 812357
Article Last Modified on 10/25/2007
APPLIES TO
- Microsoft Exchange Server 2003 Standard Edition
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange 2000 Server Standard Edition
- Microsoft Exchange Server 5.5 Standard Edition
SUMMARY
This article describes the best practices to use to maintain a healthy Microsoft Exchange Server database after you complete a repair operation on your database by using the Eseutil /p tool.
MORE INFORMATION
After you repair your Exchange Server database by using the Eseutil /p tool, Microsoft recommends that you complete a defragmentation of the database by using the Eseutil /d tool, and then complete an integrity check of the database by using the Isinteg -fix tool.
For more information about how to defragment your Exchange Server database, click the following article numbers to view the articles in the Microsoft Knowledge Base:
259851 Ramifications of running the eseutil /p or edbutil /d /r command in Exchange
192185 How to defragment with the Eseutil utility (Eseutil.exe)
317014 Exchange 2000 Server Eseutil command-line switches
182903 ESEUTIL command-line parameters
328804 How to defragment Exchange databases
If the integrity of your database is in question, you may want to export the data from your database and put the data in a new database file. The Microsoft Exchange Mailbox Merge Program (Exmerge.exe) lets you extract data from mailboxes on an Exchange Server computer, and then merge the data into the same mailboxes on another computer that is running Exchange Server.
For additional information about how to use the Exmerge.exe tool, click the following article number to view the article in the Microsoft Knowledge Base:
174197 XADM: Microsoft Exchange Mailbox Merge Program (Exmerge.exe) Information
Keywords: kbbug kbinfo KB812357
