Home > Microsoft Exchange Tips > > Temporarily circumvent the 16 GB database size limit
Exchange Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 


Temporarily circumvent the 16 GB database size limit


Serdar Yegulalp
03.02.2005
Rating: -4.30- (out of 5)


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


Exchange Server 2000 Standard Edition enforces a limit on how big the message database can be. The maximum allowed size is 16 gigabytes. If you try to insert more than 16 GB of data, you run the risk of corrupting your Exchange database.

When the database approaches the 16 GB threshold, it may spontaneously dismount to prevent a problem, and Exchange will usually log an error about the database size. Consequently, if the database hits the 16 GB limit, it becomes difficult to mount the message store long enough to remove unneeded data and perform a defragmentation.

Microsoft has created a workaround for this problem, which was enabled in the September 2003 Exchange 2000 post-Service Pack 3 rollup (see Knowledge Base article 824282), and is available by default in Exchange Server 2003.

The fix allows you to temporarily increase the size of your database by 1 GB, which usually provides enough work space for you to selectively delete data and defragment the message store so the database can be shrunk safely.

To enable this, open the registry on the Exchange 2000/2003 server computer and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS
\<server_name>\Private-<hex_string>

where <server_name> is the name of the Exchange server, and <hex_string> is a long string of hexadecimal characters that will vary from computer to computer.

In this subkey, create a REG_DWORD value named Temporary DB Size Limit Extension and set it to 1. Then remount the message store and perform any needed maintenance to bring down the size of the message store.

When this feature is enabled, Event 9657 will be logged to remind you that the temporary size limit extension is enabled. Be sure to disable the extension (i.e., set the above DWORD value to 0) when you've finished maintenance on the database.

If you're constantly exceeding the 16 GB database size limit for Exchange Server 2000 Standard Edition, you may need to rethink your message retention policy or even consider moving to Exchange Server Enterprise Edition, which allows a total of 16 terabytes in the message store.

About the author: Serdar Yegulalp is editor of the Windows 2000 Power Users Newsletter and a regular contributor to SearchExchange.com.

Do you have comments on this tip? Let us know.

Rate this Tip
To rate tips, you must be a member of SearchExchange.com.
Register now to start rating these tips. Log in if you are already a member.




Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


RELATED CONTENT
Microsoft Exchange 2000 Server
Error 1053: Exchange System Attendant service could not start
Solve server problems with the Exchange Troubleshooting Assistant tool
Move mailboxes to Exchange 2007 after Windows upgrade
Third-party tools that modify NDRs for oversized email
IP address changes for an Exchange 2000 recovery server
Exchange Server 2003 tips and tricks -- 7 tips in 7 minutes
How to enable Exchange Server public folder logging
Deciphering an 0xc103798a Exchange Server setup error code
Exchange Server error message: 'A non-delivery report with a status code of 5.4.0 was generated for recipient'
New Exchange Server installation not receiving SMTP or POP3 email
Microsoft Exchange 2000 Server Research

Microsoft Exchange Server Database Management
Why boot an Exchange server from a storage area network (SAN)?
DetachPipe: Outlook add-in tool saves and restores email attachments
How to calculate white space in an Exchange streaming (.STM) file
An affordable Exchange Server database backup software option for SMBs
Solve server problems with the Exchange Troubleshooting Assistant tool
iSCSI SAN storage for Microsoft Exchange -- 5 tips in 5 minutes
Is an Exchange 2003 offline defrag needed prior to moving databases?
How to move Exchange Server email folders to another disk on the same computer
Should you use NTFS compression on Exchange Server files?
Tame your Exchange Server transaction logs

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
E2K  (SearchExchange.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary

DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

HomeNewsTopicsITKnowledge ExchangeTipsAsk the ExpertsMultimediaWhite PapersIT Downloads
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 2004 - 2008, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts