Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Patch Manager > How to install a load balancer between the PAS and the database server

How to install a load balancer between the PAS and the database server

Table of contents

Updated: November 9, 2017


This article describes how to place a load balancer between the Primary Application Server (PAS) and the database server.


All Patch Manager versions


See Migrate a local or remote Patch Manager database to a Remote SQL Server for information about adding a database load balancer. This article describes how to point to a separate database. If the database and IP are identical, Patch Manager operates as expected without any required changes.

SolarWinds recommends placing the database balancer in the same subnet as the database. In this configuration, all connection strings are unchanged, which minimizes any changes. If the connection string between Patch Manager and the database changes, the article listed above can provide guidance. 

You can also change the connection string using DBhelpler or updating the hosts file. You can change the hostname in the PAS etc/hosts file to point to the new load balancer VIP Address. This method is an simple alternative and follows the same logic as migrating the database IP address into the load balancer. 


Last modified