Hi all
After the release of Windows Server 2012 I posted about my bleeding edge experiment with upgrading WSUS 3.0 SP2 on Windows Server 2008 R2 to 4.0 on Windows Server 2012. About 250 clients have been using the Windows Update Service on this standalone server. Updates are not downloaded to the server, but pulled by the clients directly from MS Download.
Now after about 17 months of production use, the database (on a remote 2008 R2 SQL Server Enterprise) has grown to more than 11 GB. I am surprised by this large size! So far I have been unable to find relevant information on (a) what may be the reason for having such a large WSUS database and (b) if any counter-measures can be taken. (The general hints were mostly about content, not the database, like this post.)
Any specialist desiring to increase my and the community's knowledge about the subject?
Of course I could just set up a new Windows Server 2012 R2 server, pointing to a new database but I then would loose some history ...
Thanks for reading!
/Maurice