Most everyone should be familiar with this article:http://blogs.technet.com/exchange/archive/2004/08/02/206012.aspxI have reviewed this, and I still have a question. The author states that while there is no explicit "cap" to the memory usage for the store.exe process, it is not expected to exceed 1.2 GB. The process consumes 5.0 GB of 8.0 GB of RAM and the Paging file is at 8 GB on my Exchange server. Is this still normal?Windows Server 2003 Standard R2 SP2 (x64)Microsoft Exchange Server 2007 SP28 GB RAM, Intel Xeon Quad @ 2.66Mike W.

On Wed, 14 Apr 2010 23:20:22 +0000, somadude wrote:>>>Most everyone should be familiar with this article:>>http://blogs.technet.com/exchange/archive/2004/08/02/206012.aspx>>I have reviewed this, and I still have a question. The author states that while there is no explicit "cap" to the memory usage for the store.exe process, it is not expected to exceed 1.2 GB. The process consumes 5.0 GB of 8.0 GB of RAM and the Paging file is at 8 GB on my Exchange server. Is this still normal?Is what still normal? The article is about Exchage 2003, not forExchange 2007 and 2010. Your Exchange 2007 server's fine.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVPI don't know how I missed that. Thanks for your help. See, it doesn't hurt to ask, eh?MW

>Most everyone should be familiar with this article: > >http://blogs.technet.com/exchange/archive/2004/08/02/206012.aspx > >I have reviewed this, and I still have a question. The author states that while there is no explicit "cap" to the memory usage for the store.exe process, it is not expected to exceed 1.2 GB. The process consumes 5.0 GB of 8.0 GB of RAM and the Paging file is at 8 GB on my Exchange server. Is this still normal? Is what still normal? The article is about Exchage 2003, not for Exchange 2007 and 2010. Your Exchange 2007 server's fine. --- Kind Regards , Manoj (Mandy)