Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Patch Manager > Patch Manager Documentation > Patch Manager Installation Guide > Plan for a production deployment > Determine and set up the database

Determine and set up the database

Table of contents
No headers

Complete the following checklist for the SolarWinds Patch Manager database. This checklist helps you:

  • Determine the SQL database that meets your deployment requirements
  • Gather the information required to set up and configure the database
File:Success_Center/Reusable_content_-_InfoDev/SPM/Patch_Manager_2-1-4_Installation_Guide/0030-Install_Patch_Manager/0050-Activate_the_Patch_Manager_license/checkbox.gif 1. Choose a database option

SolarWinds Patch Manager supports the following SQL databases:

  • Microsoft® SQL Server® Express
  • Microsoft SQL Server Standard or Enterprise Edition

If you choose SQL Server Express, the database is installed on the SolarWinds Patch Manager server during the installation. No additional configuration is required.

SQL Server Express has a 10 GB storage limit. If you exceed this limit, you must migrate your database to a remote SQL server.

If you choose SQL Server Standard or Enterprise Edition, you must install the database on a separate server prior to installing SolarWinds Patch Manager.

SolarWinds recommends this option to prevent a single point of failure.

File:Success_Center/Reusable_content_-_InfoDev/SPM/Patch_Manager_2-1-4_Installation_Guide/0030-Install_Patch_Manager/0050-Activate_the_Patch_Manager_license/checkbox.gif

2. Set up the database server

(Standard and Enterprise Edition only)

  1. Ensure that the server meets the SQL server requirements.
  2. Install and configure the SQL Server database software.

    See the Microsoft TechNet website for details.

File:Success_Center/Reusable_content_-_InfoDev/SPM/Patch_Manager_2-1-4_Installation_Guide/0030-Install_Patch_Manager/0050-Activate_the_Patch_Manager_license/checkbox.gif

3. Gather the database credentials

(Standard and Enterprise Edition only)

Make sure you have all account credentials, SQL database credentials, your SolarWinds account, and local admin server credentials. This includes:

  • Network path to the database instance
  • SQL Server database server hosting the Orion database (for an Orion Platform integration)

The local administrator account is not the same as a domain account with local admin rights. A domain account is subject to your domain group policies.

Last modified

Tags

Classifications

Public