Comments on: WSUS DB and large memory consumption http://ict-freak.nl/2009/06/04/wsus-db-and-large-memory-consumption/ VMware, Linux, Scripting... Mon, 21 May 2012 13:28:47 +0000 hourly 1 http://wordpress.com/ By: C T http://ict-freak.nl/2009/06/04/wsus-db-and-large-memory-consumption/comment-page-1/#comment-16667 Mon, 24 Oct 2011 10:49:10 +0000 http://ictfreak.wordpress.com/2009/06/04/wsus-db-and-large-memory-consumption/#comment-16667 This is not only important when running under ESX but also for other virtual environments.
Please note that I had to connect using a pipe instead of tcp to get a connection with sqlcmd \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
I reduced maxmem to 256 which makes it possible to run WSUS in a 2GB VM.

]]> By: Arnim van Lieshout http://ict-freak.nl/2009/06/04/wsus-db-and-large-memory-consumption/comment-page-1/#comment-10204 Thu, 04 Jun 2009 10:28:49 +0000 http://ictfreak.wordpress.com/2009/06/04/wsus-db-and-large-memory-consumption/#comment-10204 Although your solution caps the memory usage of SQL, it is not a real solution for the ballooning. The ballooning is happening because the VM is trying to use more memory then its entitled to use.
Reason is mostly because memory is overcomitted and shares come into play. To solve the ballooning investigate why memory is scarce and/or allocate less memory to the SQL VM if your capping it’s memory usage anyway.
It could also be possible that a limit on your VM is causing the ballooning to happen. See Scott Herold’s post on Limits http://www.vmguru.com/index.php/articles-mainmenu-62/mgmt-and-monitoring-mainmenu-68/96-memory-behavior-when-vm-limits-are-set.

I like the way you showed to cap memory usage on SQL however.

]]>