"eseutil /ms <dbname>" will give you the full space utilization layout of your database. It's pretty easy to write a WMI script that shows you dumpster contents too, if you really think that that might be an issue. Check out the Exchange_MailBox class of WMI. -----Original Message----- From: A. Michael Salim [mailto:msalim@xxxxxxxxxxxx] Sent: Sunday, May 15, 2005 11:27 PM To: [ExchangeList] Subject: [exchangelist] RE: Exchange 2003 store size mystery http://www.MSExchange.org/ Hi, > Even though you archived all the data out of the store, what you wind > up with is 1GB of "real" data and 53GB of "empty" data that could be > recovered through an offline defrag. I ran an offline defrag via eseutil /d, which did not recover much (maybe 8 or 9 GB not the expected 50+ GB). > You could also (depending on your configuration) have some stuff left > in the dumpster that is also taking up space, which would become white > space once you reach your retention time limits. I selected the "dumpster data" option when I exported the PST's so there should be no dumpster data left afaik. Mike ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: michael@xxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx