I don't use WSUS for SQL Server patching because we have so many different compatibility issues, requirements and downtime OLA's that it makes it impossible to deploy anything in this way - not sure of many who can to be honest.

However, we have a custom DBA 'app' that I would like to develop a snap-in for that alerts the team to any new updates released by Microsoft for SQL Server (SP's, CU's, Hotfixes etc.)

I thought, hey, let's just hook into the WSUS database, poll for new updates and display them on a web page if they exist...

It works to a fashion, but I noticed that there is a lot of missing updates in WSUS from SQL Server. For example I'm not seeing SQL Server 2014 SP2 CU1 in there which was released recently, 2014 SP1 CU7 is not there, but CU8 is. 2012 SP2 and SP3 are not their either, as another example.

We sync WSUS half-hourly, and all SQL Server products are selected.

Any idea why some SQL Server updates aren't coming through to us via WSUS? IS this normal? Do Microsoft not publish everything through WSUS?

  • Wouldn't it be easier to follow one of aggregating websites? sqlserverupdates.com for example has both RSS feed and and e-mail alerts for CU'ss and SP's. sqlserverbuilds.blogspot.com doesn't have those (at least I don't see it), but has history of releases. – Marcin S. Sep 6 '16 at 13:35
  • 1
    Yes, but no fun! Seriously though we do use both those sites to keep track as part of general review cycles - I was just trying to do something different using WSUS and noticed the gaps which seem strange to me. – Molenpad Sep 6 '16 at 15:04
  • 1
    SP1 CU7 is not there because the new policy is only to provide the most recent CU for any branch. Therefore, when SP1 CU8 was released, SP1 CU7 was removed. I would read through that article in full because it explains some other things as well (certain types of releases will be offered Microsoft Update, for example, while others will merely be listed in the Windows Update Catalog if you want to find them). – Aaron Bertrand Sep 6 '16 at 20:22
  • 1
    I don't use WSUS so I can't explain why the other releases you mention aren't there; perhaps 2016 CU1 is too new to be in the catalog, and/or perhaps WSUS doesn't know you're looking for anything other than 2014. – Aaron Bertrand Sep 6 '16 at 20:22

Actually there is a good microsoft article about it. I had the same problem and Microsofts solution fixed it. https://support.microsoft.com/en-us/help/4047327/non-applicable-sql-server-cus-are-listed-in-wsus-mu-or-confmgr

  • 1
    Please, write the gist of the solution into the answer (but keep the link, too). Links come and go, the relevant content should be in the answer. – P.Péter Jun 10 '20 at 15:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.