SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2012 Forums
 SQL Server Administration (2012)
 AppDomain unloaded by escalation policy.
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

bblankenship
Starting Member

1 Posts

Posted - 10/04/2013 :  14:47:46  Show Profile  Reply with Quote
I am running SQL Server 2012 Enterprise 64bit on Windows 2012. I have approximately 300 small databases on this server, each one running a CLR assembly. During a busy day, I get alot of out of memory exceptions with my CLR. The CLR is a simple trigger.

I have lock pages in memory set, min and max memory configured.

The server has 96GB RAM and I have 72GB set as the min and max memory. How can I tell where this memory pressure is coming from?

James K
Flowing Fount of Yak Knowledge

3326 Posts

Posted - 10/04/2013 :  15:16:00  Show Profile  Reply with Quote
Not necessarily an answer to your question, but just a few thoughts that may or may not help:


1. Setting MAX and MIN memory to the same value is not recommended. I don't know the internals well-enough to say why, I am just quoting from here. http://technet.microsoft.com/en-us/library/ms178067.aspx Nonetheless, my guess is that it is unlikely that the problem you are facing is because of this.

2. See if this article is of any use to you. My only familiarity with it is having found it via goole. I tried to read through it, but didn't really find any real recommendations in there. But, still might be useful to take a look. http://blogs.msdn.com/b/psssql/archive/2013/01/30/appdomain-unloading-messages-flooding-the-sql-server-error-log.aspx

3. The article mentioned in 2 suggests that this problem is not due to memory pressure on the server (rather due to GC kicking in too often?) - nonetheless, you might want to see if there is memory pressure on the server. Look at some of the memory related counters in perfmon. Memory Grants Pending, Page life Expectancy, Buffer Hit cache Ratio etc.

4. In SQL 2008 R2 and earlier, the MAX memory specification was max memory used by buffer pool only. CLR memory was outside of that. But in SQL 2012, CLR memory is included in the max memory setting. So unless you have other applications and services running that need 18 Gigs of memory, you may be able to increase max memory.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.05 seconds. Powered By: Snitz Forums 2000