Connect with us

Hi, what are you looking for?


Eliminate Exchange Mailbox Size Limitations

Microsoft Exchange is a server side application creating an emailing platform in collaboration with MS Outlook. Exchange has the capability to store a large number of mailboxes. All administrators know about the limited size limit of the stored mailboxes, which is an important parameter to consider when it comes to the performance of Exchange.

An experienced administrator is well aware of the fact that the server begins facing issues with speed and other performance criteria if it is loaded with huge data. Below is a close look at mailbox size limitations in different versions of Exchange:

  • Exchange 2002 offers the mailbox size limit of 16 GB

  • Exchange 2003 SP2 offers mailbox size limit of 18 GB

  • And the Exchange 2010 offers 1024 GB size limit of a mailbox.

However, the Exchange Server allows you to change the mailbox limitation according to your requirements. Let’s see how you can do it in Exchange Server 2010:

  • Click ‘Mailbox’ from the menu in Exchange 2010.

  • Navigate to the tab named ‘Database Management’.

  • Look for the target database and click its ‘Properties’.

  • Go to the ‘Limits’ tab.

  • Change the mailbox size restriction values. (Note that the value you enter is saved in KBs)

It is recommended by experts to set the size to the maximum offered limit because a mailbox may consist of thousands of emails.

However, it is not surprising that if you have not changed the size limit settings or if the defined size has been exceeded, the database files stored on Exchange get damaged or corrupt. Exchange Database files are EDB files, containing the entire Outlook data within tables. The EDB files are placed in Information Store, which is an important component of Exchange. Corruption mainly targets the two files: Priv.edb or Pub.edb, placed in Information Store. Following are the symptoms you will see when corruption in information store takes place:

  • The Information Store fails to start.

  • You fail to stop the store.

  • The Information Store does not respond.

  • The usage of CPU is 100%.

  • If you have taken a backup copy of Exchange database, and in case of corruption, restore the database from the backup using the utility ‘Isinteg’ (Information Store Integrity), the following error is thrown:

Error 4294966746: JET_errDatabaseInconsistent

In order to deal with EDB corruption, you are open to use a professional Exchange recovery software application that will repair the corrupt database and get you all the data back.

Written By

I am Data Recovery Expert from Stellar Information System Ltd and currently doing research on Outlook PST Recovery Software, Outlook Express Recovery, Exchange Recovery.



Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

You May Also Like


The many attributes exhibited by the Exchange-Outlook environment makes it one of the most demanded email platforms ever developed. The EDB file can make...