Re: Size of database seems to be really large for Number of users

  • From: Byron Kendrick <bkendrick@xxxxxxxxxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 14 Dec 2004 23:30:49 -0600

Thanks for the information.  I just did an off line defrag and reduced the
size of the database from 23GB to 12 GB.  It must have been pretty "fluffy".
I am sure there are a lot of duplicated messages out there.  I feel a little
better about this now but wish there was some way to either remove the
excess copies and put them back to a single instance or get people to store
there attachments on there home directories if they have to keep a copy.

Byron Kendrick

-----Original Message-----
From: Chris Williams [mailto:chrisw@xxxxxxxxxx] 
Sent: Tuesday, December 14, 2004 1:53 PM
To: [ExchangeList]
Subject: [exchangelist] Re: Size of database seems to be really large for
Number of users

Couple things to remember:

* Even though the database file size may be large, it could have white
space that will be used as you move users over from the 5.5 server.  So
the database file is not guaranteed to grow in a linear relationship
with new mailboxes.
* second, if you move mailboxes over one by one, you are placing them in
the new server and breaking single instance storage that they had on the
Exchange 5.5 server.  So if there were a lot of large messages or
attachments that were stored singly on the 5.5 server, there is now a
separate copy of each of those messages/attachments on the new server.  

This will work itself out over time, as those old messages are deleted.
The only way to have avoided this problem is to have done an in-place


List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
To unsubscribe visit
Report abuse to listadmin@xxxxxxxxxxxxxx

Other related posts: