Export (0) Print
Expand All
Expand Minimize

The Exchange Database exceeds 100 GB in size

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2007-01-17

The Microsoft® Exchange Server Analyzer Tool queries the CIM_DataFile Microsoft Windows® Management Instrumentation (WMI) class to determine the value of the FileSize key for each Exchange information store database. If the combined size of an information store's .edb file and .stm file exceeds 100 gigabytes (GB), a warning is displayed.

Microsoft recommends that information store databases grow no larger than 50 GB. Assuming proper maintenance, there are no operational issues with running mailbox stores larger than 50 GB; however, backup and restore times may make larger mailbox stores unsuitable for some service level agreements (SLAs).

If you run mailbox stores larger than 50 GB, verify that your hardware is matched appropriately with the service level agreement such that restoration of large databases is within your SLA. Otherwise, it is recommended that you distribute mailboxes across multiple mailbox stores so that no single mailbox store is over 50 GB in size.

  1. Consider moving some of the mailboxes from the large information store to a new information store on this or another Exchange Server computer.

  2. If you have recently moved mailboxes from this information store to another store, or if you have recently deleted mailboxes from this information store, performing an offline defragmentation may decrease the size of the files.

  3. Consider setting mailbox or message size limits to prevent unlimited growth of the information store database.

For more information about .stm and .edb files, see the Microsoft Knowledge Base article 232323, "Native Content Storage in Microsoft Exchange" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=232323).

For more information about moving mailboxes in Exchange Server 2003, see the Knowledge Base article 821829, "Moving Mailboxes in Exchange Server 2003" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=821829).

For more information about moving mailboxes in Exchange 2000 Server, see the Knowledge Base article 328810, "Moving mailboxes between servers" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=328810).

For more information about performing an offline defragmentation of an Exchange Server database, see the Knowledge Base article 328804, "How to Defragment Exchange Databases" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=328804).

For more information about setting message size limits, see the Knowledge Base article 322679, "Set Size Limits for Messages" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=322679).

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft