I would like to confirm with people who have expeeinced reachingvery close to the public folder store limit or have carried out an offline defrag. I would like to knowwhether the public folderstore can be allowed toinflate to its fullest (75 GB in my cas), but will continue to be functional provided that there is ample 'white space' or is that the maximum limit of the database and thefall over point - leading to probbalya dismounted database. Thanks

The database will function within it's available white space after the .edb file has grown to it's maximum limited size, but this is usually not common as the file doesn't increase in size until the white space is all used up. It's possible to perform some cleanup after the limit is hit but relying on white space is not a good idea and can severly limit your options when the time comes.

use these registry values to get warnings when DB size increase and get closer to your upper limit http://technet.microsoft.com/en-us/library/bb232092.aspx http://technet.microsoft.com/en-us/library/aa996177.aspx http://technet.microsoft.com/en-us/library/aa998066.aspx

Thanks - Jeff, Lasse In the past I have also noticed that the size of the 'Public Store' actually started to increase in size when I last carried out some deletion and archiving of the public folders. Have you experienced anything along these lines ?

Cant say that I have seen or observed it, but if you think about it, it's logical to happen to a certain degree. When you delete something from an Exchange DB it is not simply removed, it is just marked as deleted, and with that there is write operation and if there is no free space inside the DB, ESE must increase the file size to make room for the write operation.

It is important to note that white space does not count against database size limit, hence, offline defragmentation is not necessary. It is also important to note that due to the fact that white space does not count against database limit, when you receive alerts in event log, offline defrag will not resolve the issue. It is your content that will need to be managed. http://technet.microsoft.com/en-us/library/aa998066.aspx