Here is something I came across on the InfoPath Forms Services best practices documentation . "ASP.NET employs a strategy of targeting maximum Internet Information Services (IIS) memory use of the lesser of either 800 megabytes or 60% of available physical RAM. These settings are configurable in IIS manager. ASP.NET also monitors physical RAM use, not just for the w3wp.exe process, but for the entire system. When 80% of the physical memory on the server is committed, ASP.NET begins periodically...
It's an often DBA task to rebuild indexes for a database as part of a maintenance plan, but watch out! MOSS search DB's don't like it! This post explains it all: http://blogs.vertigo.com/personal/michael/Blog/Lists/Posts/Post.aspx?ID=4 And some official word from the Knowledge Base: http://support.microsoft.com/kb/930887/en-us I've read somewhere that SQL SP2 fix this (can't recall where), can someone confirm this?