Large Database warning on Exch 2003

Hi guys, hope you can help me!

We have an exchange 2003 server with server 2003 OS, and i ran the Microsoft Exchange Server Best Practices Analyzer Tool, and received the following message:
Large database warning: The mailbox store "User_Storage_2 on server NJLAWMAIL04 is 104GB in size. It is recommended that the maximun database size does not exceed 100GB

should this of a concern? and how do i fix this?

J MolinaIT AdminAsked:
Who is Participating?
Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
There is a registry key to edit to allow the increased size of the DB.   I take it you have Exchange 2003 Enterprise?

It is suggested to maintain or limit the Database size to 100GB, b'cas it is much easier to recover the database during recovery purpose and also it takes lesser time to complete online maintainence.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

JamesSenior Cloud Infrastructure EngineerCommented:
The space is logical - so a physical store of 100gb is not a problem if you have more than 5gb of white space in the store. The size of the store would have no impact on the users in Outlook, unless your storage was badly configured. I have built and maintained servers with stores over 250gb in size and they were fine - because the storage was configured correctly.
However you are correct on the behaviour of the database if you removed all of the content. The simple rule is that the Exchange database never shrinks in its physical size.

I am in the middle of a blog posting on this subject, so I have some text to hand.

The EDB file should be thought of as the MAPI database and will consist mainly of internal email.
The STM file should be thought of as the SMTP database and will consist mainly of external email.

What tends to happen when there is a data base purge is that internal email is deleted, but more external email arrives, so there is a mismatch.
Do you receive lots of attachments from external senders?

As for the IFS files, do not delete them.

JamesSenior Cloud Infrastructure EngineerCommented:
Because there are whitespaces in the edb file, these happen when stuff is deleted.

Deleting items does not reduce the size of your database

Only way to do that is by doing an offline defrag of the database however you would need the space to have 2 database which it appears you do not

Hi jbm,
You can have up to 4 storage groups with 4 databases in each storage group. It is recommended you split your mailbox store into smallers ones. By doing this your database sizes will be smaller, which in turn will speed up backup/recovery of a database, and also, should one database go down, you will not lose your whole Exchange system.
To create the mailbox stores, right click on your Storage Group, and select New... Mailbox Store. Once you have created it, you can then click on a mailbox in ESM and move it to the new mailbox store.
Once you have moved half the mailboxes, you will need to run a offline defrag (eseutil) on you current mailbox store to reclaim the disk space.
perfectly said Harkins
J MolinaIT AdminAuthor Commented:
thank you guys, your notes was very informative, but i need steps...
Do you have a single mailbox store?
J MolinaIT AdminAuthor Commented:
no, i see there 2 mailbox stores
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.