TERMS
This document and what comes with it are provided as-is with blunt warning: Use at your own risk, buyer beware.You break your system; you own the resolution as well. We have no liability for what you do, or can't do, or fail to do with this information. Your entire protection is to start over again with a protected backup, or from protected system. If you don't want to accept this idea, please don't use this document.
OK, one step at the time. Please, remember that with Server 2008 you have x64 product that has a lot more requirements then 2003 x86. Can you do the following:
- Open the task manager on that server and choose processes from all users. Click Yes if the UAC pops up.

- Double click on the memory colomn to sort at highest memore use.

- Highlight the image that takes so much Ram and right click and choose Go to Service. This is one the reason Server 2008 is soooo much easier then 2003 :-)

- Aha! It is the Internal Database...in my case. Now I want to know about that server with the high memory usage. Which SQL instance is causing this?
