Excess Total Committed Memory needed is X KB, threshold value for this monitor is 131072 KB - can this be a normal operating state?

Excess Total Committed Memory needed is X KB, threshold value for this monitor is 131072 KB - can this be a normal operating state?

Hi all,

I am receiving errors on several of my SQL Servers indicating " Excess Total Committed Memory needed is X KB, threshold value for this monitor is 131072 KB". From the research I've done, this is the difference between the Target Server Memory and the Total Server Memory. If I'm understanding correctly, this alarm fires because the difference between the target memory and the actual amount of memory the server has committed using the memory manager is more than 128 megs. In a "normal" situation, the target amount and the actual amount committed should be relatively close, and the alarm fires if this condition isn't true. In short, the alarm says, "hey, we're trying to use this much memory, but we aren't using it all; what's going on?"

The question I have is whether it's a "normal" condition on some servers to have this alarm firing all the time? Say, for example, I have a seldom-used database that in its entirety takes up 1 gigabyte of space on disk, and can in turn be completely loaded into memory. Let's say that I have 64 gigs of RAM installed in this computer, and set the maximum server memory to be 50 gigs.  In this situation, the total amount of memory committed using the memory manager is likely never going to reach 50 gigs, or anywhere near it. This is a "normal" condition for the SQL server, but OpManager is going to indicate there are problems. Am I understanding this correctly, or should I be taking actions to remedy this error on such machines? Thank you very much for your time.

                New to ADSelfService Plus?