CPU Usage Reported By Profiler

  • Just having CLR enabled consumes a surprisingly large amount of VAS (I can't quantify exactly how much) - it would be worth disabling CLR then restarting SQL Server if you are sure that you're not using it.

    Chris

  • Having CLR enabled and loaded consumes around 100MB of VAS.

    Another point to bear in mind is that CLR can be loaded even when disabled - some of the internal MS procedures use it and will force it to be loaded if called...sp_browsereplcmds if one IIRC.

    32-bit and SQL Server is not a happy combination, even without hosting the CLR.

Viewing 2 posts - 31 through 31 (of 31 total)

You must be logged in to reply to this topic. Login to reply