.NET Framework execution was aborted by escalation policy because of out of memory
The issue was resolved by doing the below changes on our environment
1. Adding service account to lock pages in memory
2. Adjusting Min and Max Memory in optimized way.
CLR memory consumtion comes outside of buffer pool, by configuring max memory in optimized way to give enough memory for CLR.
The issue was resolved by doing the below changes on our environment
1. Adding service account to lock pages in memory
2. Adjusting Min and Max Memory in optimized way.
CLR memory consumtion comes outside of buffer pool, by configuring max memory in optimized way to give enough memory for CLR.
What version of SQL are you running that this resolved your issue?
ReplyDeleteSQL Server 2008 R2
Delete