I run SBS 2003 with SP2 and the Exchange is on a differnt disk. I recently migrated the PRIV.edb and PRIV.stm from one disk to a new bigger disk on a RAID 5 configuration and have found that the date and size of these databases are not changing. Would someone know why and if so, how to resolve this. When I look at the Event logs, the Event ID 220 showing the beginning of the backup size of the Info Store is the same as when I moved the databases - this is 11 days ago. I have stopped the Info Store once and restarted and it registered the change but then does not keep updating it! A problem associated with this (perhaps) is that before transition, opening of Outlook was fast and the mailboxes showed quickly on the client PC's. Now it takes a long time. Considering that the new disk has a lot of free space and is used solely for Exchange data, one would assume that it would be faster - not slower! Any ideas anyone? Thanks in advance. P

hi,what do you mean when you say , outlook is slow. Is it slow while opening for the first time time or it is slow while sending and recieving emails.Check for RPC counters on the servers and see if you have disk bottle neck. This is just to identify , if the new disk is creating issues for you.Raj

Hi, Regarding the database size, I suggest you read following article firstly: Understanding Exchange Databases Disk Consumption http://www.msexchange.org/articles/Exchange-Databases-Disk-Consumption.html Regarding the edge file date modified stamp, I do not find any public document currently. Nevertheless, here is the response from our internal discussion group: In some cases, the date modified only updates when the file expands. So it is common to see an older (meaning it is less likely to expand) in use DB not update its date modified for quite a while. There might be other cases as well, but regular writes that do not expand the file do not update this in some cases. Mike Shen TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

Thank you Mike - A colleague sent me this which corroborates with the article: EDB files are Exchange DataBases. To prevent the need to constantly resize, database files contain "white space". Once the white space is filled, the file will be made larger (usually by a preset increment). For the same reason, removing email does not reduce the file size. To all intents and purposes this means that database files only get larger unless a defragmentation routine is run. I think I can have a sigh of relief. However, this does not explain the slowness in accessing the database via Outlook through a client PC. Any ideas on this?