SCCM SUP SUSDB on sql express edition running out of disk space post every software update synch

Question

We have setup a new SCCM secondary site which also hosts SUP SUSDB role configured on the SQL express edition which gets installed along with secondary. The problem is on monthly software update synch the SUSDB size crosses 10 GB limit & synch fails. Server is running on windows 2016 OS & SQL expression edition version is 2016.

I have 3 other SCCCM secondary sites which are running in the same way as mentioned above but the only difference is that servers are on Windows 2012 R2 OS & SQL expression edition version 2012. Here i dont see this SUSDB growth behaviour.

Is there some change when it comes to SQL express edition version 2016 & 2012 when it comes to SUSDB?

Appreciate if someone answers.

Answer 1

Your question would be better asked on the SUS forum.

Please tag your post: windows-server-update-services

Answer 2

Hi,

I suggest you post your question in the dedicated forum--Microsoft Endpoint Manager forum. It is more appropriate and more experts would help there.

Also please check following links if help:

Configuration Manager site sizing and performance FAQ(When should I use full SQL Server instead of SQL Express on my secondary sites?)
https://learn.microsoft.com/en-us/mem/configmgr/core/understand/site-size-performance-faq#when-should-i-use-full-sql-server-instead-of-sql-express-on-my-secondary-sites

https://social.technet.microsoft.com/Forums/ie/en-US/73472558-125c-49e3-94c5-9f7bc2bc8984/db-is-10-gb-but-data-is-not-stored-locally-whats-taking-up-the-space?forum=winserverwsus

===============================================

If the response helped, do "Accept Answer" and upvote it.

Answer 3

Are you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.?

https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

This is one of the reasons why I don't recommend using the SQL Express edition. WID or Full SQL. The WID is very capable of handling it.