If ESEUTIL /D was executed against a database the. For a trip down memory lane there is an excellent read in this document Determining the True Amount of Space in an Exchange Database Event 1221 does not review this shiny streaming thingymabob, and did not report what free space may have been available within the. The intent was to store native RFC content in the streaming file as the Internet was the future and content would be converted between the. Things advanced, the dotcom bubble popped and with the advent of Exchange 2000 the streaming file was introduced. Free pages that are owned by other tables in the database are not taken into account. Event 1221 estimates free space by calculating the number of empty pages owned by the messages table, the attachments table, and the database root. All space in an Exchange database is owned either by the database root or by particular tables in the database.
Defrag exchange 2010 database Offline#
If you perform offline defragmentation, you will recover at least the amount of space that is reported as free. More on this later….Īs mentioned in the KB, the free space that is reported by Event 1221 is a conservative estimate. Life was indeed simple and good! Additionally Exchange 5.5 SP1 also added a second enhancement for determining white space which was the ESEUTIL /MS switch to dump out the space consumed by tables in the database. Event ID 1221 would then report on the white space contained within the database file.
Standard Edition could have a database of up to 16GB, and Enterprise had the “unlimited” database. In those simple Exchange days we would have one Public Folder (pub.edb) and one Mailbox database (priv.edb) per server. This event was introduced in Exchange 5.5 SP1 back in August 1998. This event would tell us the amount of white space within the database. In ye olden days when Exchange admins went to work on horses (alright, iron horses), we would look for the venerable application event log entry 1221. Historical Approach To Checking White Space