The Exchange Server Database Utility (ESEUtil.exe) is an inbuilt command-line utility in Exchange Server. ESEUtil can be used for viewing, repairing and modifying an Exchange database. Microsoft recommends ESEUtil tool to perform database recovery and repair operation. But there are some serious limitation attached with ESEUtil tool which sometimes cause problem.
#1 Data can be permanently lost During recovery process performed by eseutli /p command in Exchange Server, there is a possibility of losing all the important data stored in edb file. As eseutil p command permanently deletes those data what it can’t recover and then there is no way you can have them back. So, you should create a backup first before performing any operation using eseutil. #2 ESEUtil requires lots of free space to perform its operation eseutil /p command requires atleast 20% free space while eseutil /d requires 110% free space in order to perform its operation. Most of the time the size of database is so huge that it is impossible to create free space. #3 Inconsistency after running ESEUtil command Most of the time you need to run isinteg command to remove any inconsistency created by eseutil utility. But sometimes the error counts never comes to zero and you need to run isinteg repeatedly. #4 Time Consuming Process ESEUtil utility took so much time that you can’t believe. And if the size of database is high this makes the situation even worst. So, if you like to recover data in time, then think twice before using eseutil command. #5 Complexity at its best Even if your hard core professional in Exchange Server, you might get stuck sometimes while working with eseutil command. Since there are endless command associated with powershell and no GUI, it is very hard to recover database properly.
Tips For Exchange 