SQL Server Performance

CLR Job Maxing out server resources

Discussion in 'SQL Server 2005 CLR' started by sql_jr, Aug 9, 2007.

  1. sql_jr New Member

    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!
  2. satya Moderator

    How was the data created? It is important to communicate how the above data was calculated.
  3. sql_jr New Member

    Currently, our server is on SQL Server 2005 SP2, build 3042. Since then there have been serveral post-sp2 hotfixes. The latest cumulative one is build 3161. This includes a fix for: High CPU utilization by SQL Server 2005 may occur when you use NUMA architecture on a computer that has an x64-based version of SQL Server 2005 installed -
    http://support.microsoft.com/kb/931821/ What are your thoughts? Many thanks!
  4. satya Moderator

    Good to know latest service packs are installed, you might refer to the post SP2 builds that are release recently... http://support.microsoft.com/kb/933097 (an example) or their readme files.
    But still good to know why this CLR is used very much.

Share This Page