I've only just noticed (Server 2003, SQL2005, 64 bit) that my RMS has almost no physical memory left after about a week of running (32GB server). The pagefile grows to around 30Gb too. After doing a little guesswork, I bounced the MSSQLSERVER service, and voila! almost all of the memory (~25GB) is returned instantly and the RMS hardly misses a beat. So, is this a known problem with SQL2005 with other users running Windows 2003, 64bit, and if so, is there a fix? I can only think that it may relate to either a recent MP download or a hotfix form MS. It does not seem to be a problem with other 2005 DB servers we have here. Thx, John Bradshaw

I'm not an expert on how SQL Server consumes memory, but I think, by default, it will consume what's there. Here are some explanations, http://www.sqlservercentral.com/blogs/glennberry/archive/2009/10/29/suggested-max-memory-settings-for-sql-server-2005_2F00_2008.aspx. /RogerThis posting is provided "AS IS" with no warranties, and confers no rights.

Thx Roger. I haven't seen this in any SCOM forum/blog so far and I'm hesitant to apply this. Is it something you have done for your environment? How do you figure out the max value to set? Cheers, JB

Hi JB! Like I said, I'm no expert. We have dedicated SQL-clusters that our SQL-guys have set up. If I where you I'd go over to the SQL forum and ask the question. Most likely max value depends on a number of factors. For OpsMgr (I assume you are co-locating the RMS with SQL) you need headroom for the RMS, for the OS etc. Regards Roger This posting is provided "AS IS" with no warranties, and confers no rights.

Thx Roger JB