Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

i just want to check something.

i always thought that a full sbs 2003 backup (through backup wizard) actually optimized the database of the exchange server.

i was curious to see if you would suggest maybe doing an exchange database optimization after a full sbs 2003 backup or just before a full sbs 2003 backup.

i wanted to play around iwth the optimize interval on the system manager tab.

thanks. gd

share|improve this question
up vote 2 down vote accepted

As an SBS MVP, I've learned through long experience that if Microsoft hasn't enabled a feature in the SBS setup, then it is probably not a good idea to tinker with it. SBS is a complex product with lots of subtleties. It's best to stick to using the SBS configuration consoles and not to stray outside them. Lots of 'enterprise' guys fall into this trap and live to regret it.

Unless you really have clear evidence that your exchange database needs optimising, then I'd apply the maxim "if it ain't broke, don't fix it".

share|improve this answer
+1 for that point. We all love hand-crafting our config files byte by byte, but I love consistency and repeatability more. I can't see the average SBS shop having enough email to cause a real problem if it isn't optimized. (I'm presuming the OP wants to change when Exchange goes through the DB and cleans up unused pages, which is usually done in the early hours of the morning out of the box.) – dmoisan Aug 26 '09 at 23:49

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.