• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 980
  • Last Modified:

exchange enlarge database size, log files

I have a few questions regarding for the exchange enlarge database size, log files and database file.  We have a exchange 2003 std server with sp2. C drive has 12 G, and D drive has 394 G

1 I need to enlarge the database size, how do I allocated the size of 75 G?  Does it goes Private-GUID + Public-GUID = 75 G (eg 40G of mailbox + 35G of public folder = 75G), or Private-GUID and Public-GUID both all can be configured as 75G? Same question as Buffer percentage. If I would like set buffer size is 20%, which means either mailbox store or public folder store reaches till 80% will use buffer size or total of these 2 stores reach till 80 % will use the buffer size? By the way, In our school, mailbox size enlarge much quickly than the public folder. Should set up different buffer size and different database size?

2) Do log files and database files should be located on the same drive or different. Which way is the best?  By the way, all .edb and .stm files on the D drive now. I am wondering if I can leave the log files the default location on C drive?

3) Does the log file have the size limited?

Thank you very much for the help!!!

1 Solution
The registry settings are per database. Therefore you have settings for public and settings for private. Therefore the total size of the stores can be 75gb each.

Transaction logs should ideally be stored on a separate physical drive/array from the transaction logs. If you have everything in one array then you are not gaining anything by moving them, other than the space gain. There will be no performance increase.

Log files will keep growing until you either do an Exchange aware backup or run out of space.


This article explains this really well: -

Explaining the Database size limit changes in Exchange 2003 Service Pack 2

1. The 75GB limit is per database. Therefore you can have a 75GB mailbox store and a 75GB public folder store. The buffer sizes are independant also.

2. You should place the transaction log files on a seperate redundant disk to the database files. The transaction logs store user data that has not been committed to the database. Therefore in case of a disaster you would restore the database copy from the last Exchange aware backup you ran and then use the transaction logs to roll the database forward to the point in time when the failure occured in order to obtain as much data that is available in the logs since the last online backup.

3. The log files for Exchange 2003 are 5MB each and are created as needed by the system. There is no limit on the number of log files but once your drive that contains the log files fills up the Exchange information store dismounts the databases as their is no space available to write the data. Therefore you need to ensure that your Exchange aware online backups are working and purging the transaction log files each night.

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.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now