Once a user accesses information that is stored in the STM from a MAPI
client (outlook) we will promote the information from the STM file into the
EDB file. So basically you do not really need to worry about the size of
the STM file in relation to the EDB file. Now there maybe additional white
space in the STM file that we should be able to recover using an offline
defrag.
eseutil /d <path to priv1.edb> (this will do the edb and stm)
328804 How to Defragment Exchange Databases
[url]http://support.microsoft.com/?id=328804[/url]
Hope this helps,
Please read Chapter 10 Microsoft Exchange Information Store Service
Architecture from Exchange Server 2003 Technical Reference Guide for more
understanding of stm and edb files.
<HAVOK> wrote in message news:43m1j1hkoob5qbbrf...@4ax.com...
<HAVOK> wrote in message news:43m1j1hkoob5qbbrf...@4ax.com...
<HAVOK> wrote in message news:qn28j1tf27rplt7sh...@4ax.com...