Hello, I have the same Issue.
any call of clr function returns me:
Failed to initialize the Common Language Runtime (CLR) v2.0.50727 due to memory pressure. This is probably due to memory pressure in the MemToLeave region of memory. For more information, see the CLR integration documentation in SQL Server Books Online.
So i started to find a way to understand , monitor, and correct what the .. is going on.
His query returns me the info
Total avail mem, KB
8 563 879 544
Max free size, KB
8 558 731 520
=> ~5go, which suggested me the Pb was not coming from here...
For me it's seems an issue of SQL 2008 fixed in 2008 R2, because:
SELECT type, virtual_memory_committed_kb, multi_pages_kb
WHERE virtual_memory_committed_kb > 0 OR multi_pages_kb > 0
type virtual_memory_committed_kb multi_pages_kb
MEMORYCLERK_SQLCLR 12548 38936
MEMORYCLERK_SQLSTORENG 23872 30328
MEMORYCLERK_SOSNODE 0 13512
MEMORYCLERK_SQLSTORENG 0 3456
MEMORYCLERK_SOSNODE 0 3440
MEMORYCLERK_SQLGENERAL 0 3408
which bring me to http://support.microsoft.com/kb/959767/en-us/
I don't like to patch the production server on run.. And i will migrate for R2 in few months.
So I'm very interesting about reset the VAS or clean the allocated pages on run == without restarting ..
For the moment, I think I 'll have to wait the 'maintenance time' to reboot the services with \g. ..so plan this at 4 AM or
This MEMORYCLERK_SOSNODE are probably coming from a previous error on call of one CLR function (a regExp CLR function call on a column which no more exists)
I am not sure I'm thinking this right, if you found more info on this issue to give me a better understanding of the issue, i would be very grateful.