WSUS 3.0 Is Still A Memory Hog

This evening I brought my WSUS server up to WSUS 3.0. Mostly I wanted to see if it still was as big a memory hog as 2.0. After the 90-minute-or-so installation was finished, here is what I had:

wsusservice: 50 MB
IIS worker process: 100 MB
SQL 2005 instance: 400 MB

That's over half a gig! For a single service! In SBS land it has been standard practice to throttle SQL Server down a bit as there are other things running on the servers, so I decided to try it.

There is just one snag: WSUS ships with the "Windows Internal Database", i.e. SQL Server 2005 extremely lite. There are only three binaries in it, including exactly zero management tools. There is nothing you can use to run the commands to throttle it.

Fortunately, I had an installation of SQL Server 2000 SP4 still on this server. That install came with OSQL.EXE, the command-line SQL query/adminstration tool. It works against SQL 2005 too. The following command seems to do the trick. It remains to be seen how well it works:

C:\Program Files\Microsoft SQL Server\80\Tools\Binn>osql -E -S <server name>\MICROSOFT##SSEE
1> sp_configure 'show advanced options', 1;
2> reconfigure;
3> go
Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
1> sp_configure 'max server memory', 256;
2> reconfigure;
3> go
Configuration option 'max server memory (MB)' changed from 2147483647 to 256. Run the RECONFIGURE statement to install.
1> exit

If you want to return the server to the default run the same command, but specify 2147483647 for the "max server memory" instead of 256. If you want a different maximum memory size than 256 change it. The value is specified in megabytes.

Published Sun, May 6 2007 10:59 PM by jesper
Filed under:

Comments

# Anne Stanton said on 17 May, 2007 05:25 AM
Ah yes.. BUT what if SQL 2000 SP4a was never installed? any other options?
# Fargii said on 23 July, 2008 02:37 AM

I was always able to throttle (BTW: very apt jargon, "throttle") down sql server instances on my sbs box. It always seems to be sql server instances at the top in task manager. For a few days, I thought there was no way out with this WSUS 3.0 Windows Internal Database. Your post came to my rescue. Good stuff. Thanks!

# nino El Greco said on 26 November, 2008 02:49 AM

Very helpful, but, how do we connect the WSUS database on the new SQL Installation? We just run a simple installation and that's it?

Can you give me some help people? I am not an advanced user of SQL.. *shy*

Thanks!

# wloo said on 20 February, 2009 07:45 AM

The only(?) way I see in this environment is the following: 1. Create a share of the binary directory of any other SQL server installation. 2. Map this share of the WSUS System. 3. Use ist like jesper suggest (note that the osql command differ between "localhost", the IP and the real machines name!

@jesper: THNX for the 1st part :)