October 15, 2010 at 12:21 pm
I'm getting the following error in the SQL ERRORLOG:
AppDomain 2 (dbName.dbo[runtime].1) is marked for unload due to memory pressure.
AppDomain 2 (dbName.dbo[runtime].1) unloaded.
How can I find out which CLR assembly this is?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
February 4, 2011 at 9:07 am
Hi,
Look at these:
sys.assemblies
sys.dm_clr_appdomains
sys.dm_clr_loaded_assemblies
You should be able to find out what you need.........
February 4, 2011 at 9:12 am
Thank you, I will look at these.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
February 4, 2011 at 9:24 am
Try looking at this to watch your memory problem:
select * from sys.dm_os_memory_clerks where type = 'MEMORYCLERK_SQLCLR'
February 4, 2011 at 9:53 am
davidc-702140 (2/4/2011)
Try looking at this to watch your memory problem:select * from sys.dm_os_memory_clerks where type = 'MEMORYCLERK_SQLCLR'
When I run this on my server I get that virtual_memory_reserved_kb = 6,322,496, or over 6 GB.
Is this the amount of memory reserved on the server by the CLR at that particular moment?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply