Ok, we have a super-server 64-bit, 12GB RAM, 8/16 procs, etc., yet when one user runs a calculation job invoking th CLR (a call to a .dll, using UNSAFE ASSEMBLY, btw) it usually maxes out the CPU, after it begins to page out to disk, and the only way to get the server back is to REBOOT. We have screen shots that show although there is 8 additional GB of RAM available, its still pages out. Explanation?How would we go about troubleshooting this and discouraging using unsafe assemblies.Another thing is after it comes back, while the job activity monitor/agent says the job is stopped/completed/cancelled, the job history has the green play button and says in-progress - (any reason/concern about this? Is it just a bit flag, or is it really in progress?)Most important the OS Windows 2003 is on SP1, we will be applying SP2 this evening - any known memory leak issues?Thanks!