Generally speaking, if Patch Manager is on a dedicated server, it will work fine with the local (installed by default) instance of SQL Server 2008R2 Express Edition.
Exceptions to this would be driven by a large number of computers involved in WMI-based asset inventory collection, a notably large WSUS environment (e.g. many replica servers with thousands of clients), or heavy usage of PM task events. In these scenarios, you may find it beneficial to deploy the database on a dedicated SQL Server Standard Edition instance. There's no performance reason for deploying to a SQL cluster.
In a Configuration Manager environment, if you only plan to use PM for 3rd party update resources and *occasional* client management tools, the local instance of SQL Express will be just fine. If you envision a significant amount of usage of the client management toolset, then you may want to consider deploying the PM database onto the SQL Standard instance supporting Configuration Manager.
Great. Thanks for the information Lawrence. I’ll get with our DBA group and see the best way to configure the DB based on there requirements.
Sr. Operations IT Specialist
IT Technology Services
Office #: 713-420-4832
Cell #: 832-594-7287
Fax #: 713-445-8422
image001.jpg 2.0 KB