Online Defragmentation (OLD) should ensure that the used parts of the
database aren't fragmented, so the disk head shouldn't seek back and
forth much.
Offline defragmentation will shrink the file on disk most of the time
(there are a few odd cases where it doesn't shrink, or gets slightly
larger). There shouldn't be horror stories for `eseutil -d`. Repair on
the other had (`eseutil -p`) is lossy, and can easily cause
headaches. Repair is 'more than enough rope to hang yourself'.
I don't know if Exchange5.5 needs frequent offline defrags. Older
versions definitely needed them often.
It's likely you're experiencing just 'normal' performance
problems. Typical things to check out are:
-is it only slow when everybody is using it (typically occurs in the
morning when people arrive at work)
-network bandwidth. Do you have enough hardware?
-is the server overloaded? Is it swapping to disk? Are other processes
running on it? Do you have 'enough' memory and cpu (where 'enough' is
highly subjective)?
-does Exchange run fine when you first start the service, and does it
slow down the longer you run it? Is it fast if you stop&restart the
service? Or is it always slow?
perfmon is your friend. It's got a pretty lousy UI, but it can tell
you lots of iteresting information. The Exchange-related coutners are
under 'Database'.
You can enable extended Exchange counters by adding the 'Squeaky
Lobster' key. I tried a google search for it, but it no longer seems
to come up. The counters aren't secret -- but they provide information
that will probably just confuse most people. The 'Squeaky Lobster'
term was just chosen one day at lunch.
To get the enabled counters:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ESE97\Performance
REG_DWORD
"Squeaky Lobster" (without quotes)
set it to 1.
-martin
Boring-but-necessary-disclaimer: This posting is provided "AS IS" with
no warranties, and confers no rights.
In article <130201c2edc3$d3a7a460$a401...@phx.gbl>,