Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Patch Manager > Patch Manager 2.1.4 Administrator Guide > Wake on LAN > Configuring the Patch Manager Databases

Configuring the Patch Manager Databases

Table of contents
No headers
Created by Caroline Juszczak, last modified by MindTouch on Jun 23, 2016

Views: 2 Votes: 0 Revisions: 3

When you install Patch Manager servers, you have several options to configure the database. Patch Manager supports the following configuration options:

  • SQL Server Express on the Patch Manager server
  • SQL Server on the Patch Manager server
  • SQL Server on a remote server

The purpose of the Patch Manager database is to store all consolidated data from WSUS Inventory, Managed Computer inventory, and Discovery tasks. To report on that data, the Patch Manager console pulls the data directly from the database. To ensure optimal performance, SolarWinds recommends the following:

  • Use SQL Server 2005 Express Edition SP3 (included with the Patch Manager installer) for Patch Manager servers that require 4GB or less of storage space.
  • Use SQL Server 2008 R2 Express Edition (available from Microsoft) for Patch Manager servers that require less than 10GB of storage space.
  • Use a licensed version of SQL Server for Patch Manager servers that support multiple console users, inventory multiple WSUS servers, or execute simultaneous WMI-based tasks. These scenarios are all particularly heavy on reporting services.
  • Use a remote database server for Patch Manager servers that reside on a WSUS or ConfigMgr server.
  • Deploy additional Management role Patch Manager servers to split storage requirements between each additional server.
Last modified
01:13, 23 Jun 2016

Tags

Classifications

Public