June 11, 2015 at 3:42 am
I have been having issues with our SQL server for awhile now. It seems to run out of memory every few days and when I look at the memory dump, the MEMORYCLERK_SQLOPTIMIZER seem to take over memory and eventually cause the server to crash.
Here is the SQL verison we are using: Microsoft SQL Server 2012 (SP1) - 11.0.3460.0 (X64) Jul 22 2014 15:22:00 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.2 (Build 9200: ) (Hypervisor)
It is on a VM on Windows 2012 server. It has 20gb of RAM allocated to it and the MAX Server Memory is set to 16.5gb.
I have seen the MEMORYCLERK_SQLOPTIMIZER grow to about 11gb at the time of the server crash. Does anyone know why that is happening? What is causing the memoryclerk_sqloptimizer to get so high? I have looked it up and it looks like it has to do with ad hoc requests, but is there something I can do to bring that memory down when it gets so high so that I can prevent a server crash?
Do we just need to add more memory or is there a memory leak somewhere? Any help is greatly appreciated.
June 11, 2015 at 7:28 am
This seems to be the same question as you asked here: http://www.sqlservercentral.com/Forums/Topic1692950-2799-1.aspx.
It's easier for us to help if all the contributions are on one thread instead of scattered across multiple threads. Since you've already gotten some responses on the previous thread, perhaps we should stick to that one 🙂
Cheers!
June 11, 2015 at 9:31 am
I wasn't getting many replies from the other thread and I had some different questions on this thread.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply