Hi, Is there a known problem with memory leakage for Windows 2008R2/SP1 and SCOM on the RMS(which is running SQL2008r2)? In monitoring ~500 servers, memory usage starts at about 7-9GB and within 4 days has climbed to 23-25GB. I have no idea how to find what is causing this. Can anyone pls help? (A 2ndary MS which is where 99% of the client agents point to, seems to happily tick away with only 4gb ram (Virtual box too).... Is this an SQL issue? (Oh, and Windows Update has been run to make sure all apps are up-to-date) Thankyou, John Bradshaw

Hi John, Can you check with a perfmon for topX memory consumers? There was some issues with leaks in WMI (http://support.microsoft.com/kb/977357 and http://social.technet.microsoft.com/wiki/contents/articles/list-of-wmi-related-hotfixes-for-windows-7-and-windows-server-2008-r2.aspx). Also, it could be a normal SQL Server behaviour if SQL Server is not set up for limitingit's memory...http://OpsMgr.ru/

Thx Alexey...Shall have a look and let u know.... JB

Hi John, Do you mean all the monitored computers encounter this issue? If possible, please check Task Manager on the problematic computers and see which process causes the memory leak. Regarding this issue, please also refer to the following posts: WMI leaks memory on Server 2008 R2 monitored agents http://blogs.technet.com/b/kevinholman/archive/2010/06/09/wmi-leaks-memory-on-server-2008-r2-monitored-agents.aspx Getting lots of Script Failed To Run alerts? WMI Probe Failed Execution? Backward Compatibility Script Error? http://blogs.technet.com/b/kevinholman/archive/2009/06/29/getting-lots-of-script-failed-to-run-alerts-wmi-probe-failed-execution-backward-compatibility-script-error.aspx If the issue persists, please check the Event Log on the problematic computers; if there are any related errors, please let us know the details. Hope this helps. Thanks. Nicholas Li - MSFT Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

If SQL is installed - this is normal. SQL will consume all the the available memory on a server for use in buffer cache. If this SQL server has other applications installed, such as the RMS role - then you need to limit the amount of memory allocated to SQL so it will leave RAM available for other applications as they need it without having to release memory on demand.Kevin Holman http://blogs.technet.com/b/kevinholman

Thx very much. Couldn't see any obvious problems, so I guess I need to reign in the memory available to SQL cheers, JB