There are some interesting reading in the supported configurations for WSUS in Server 2012 which is useful to know when you design your Configuration Manager 2012 environment with a Software Update role. I normally use the same SQL for WSUS as I use for Configuration Manager 2012 in many designs at customers. However there are some interesting reading on Technet about supported databases.
Updated 2013-03-05!!
Right now Microsoft SQL Server 2012 is not supported so keep that in mind when upgrading your SQL or designing your Configuration Manager 2012 SP1 environment.
SQL Server 2012 is now supported by WSUS in Server 2012
- Windows Internal Database (WID)
- Microsoft SQL Server 2008 R2 SP1 Standard Edition
- Microsoft SQL Server 2008 R2 SP1 Enterprise Edition
- Microsoft SQL Server 2008 R2 SP1 Express Edition
- Microsoft SQL Server 20012 Standard Edition
- Microsoft SQL Server 20012 Enterprise Edition
- Microsoft SQL Server 20012 Express Edition
More information can be found here: http://technet.microsoft.com/en-us/library/hh852344.aspx
Another tip: the same article contains the recommended ant-virus exclusions for WSUS, which is highly recommended from a performance perspective. Note that the content directory is not heavily used when using WSUS with Configuration Manager.
- \WSUS\WSUSContent where \WSUS\ is the location of the WSUS content folder
- %windir%\wid\data
- \SoftwareDistribution\Datastore (for client only)
- \SoftwareDistribution\Download
The Technet article (http://technet.microsoft.com/en-us/library/hh852344.aspx) is updated February 14, 2013 and now contains in “WSUS database requirements”:
Microsoft SQL Server 20012 Standard, Enterprise and Express Edition
If you want to be prepared for the future please use the 20012 version of SQL server :) There’s no information about using SP1 for SQL server 2012, do you think it will cause any problems?
Well Spotted!
It would normally mean that they haven’t tested sp1 yet, so hard to tell.
I will update the post, or write a new one! 😀
/Jörgen