Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Patch Manager > Patch Manager Documentation > Patch Manager 2.1.5 Administrator Guide > Wake on LAN > Configure the Patch Manager databases

Configure the Patch Manager databases

Table of contents
No headers
Created by Caroline Juszczak, last modified by Steve.Hawkins on Jul 09, 2018

Views: 621 Votes: 0 Revisions: 5

The Patch Manager database stores all consolidated data from a WSUS inventory, managed computer inventory, and discovery tasks. To generate a WSUS inventory report, the Patch Manager Administrator Console pulls the data directly from the database. 

When you install your Patch Manager servers, you have several Microsoft® SQL Server® database configuration options. You can install:

  • 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 a free version of SQL Server Express (included with the Patch Manager installer) for Patch Manager servers that require 10 GB or less of storage space.

    If you exceed 10 GB, you must migrate your database to an SQL Server instance.

  • 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 hosted on a WSUS or SCCM (ConfigMgr) server.
  • Deploy additional Management Server roles to split storage requirements between each additional server.
Last modified