Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Network Performance Monitor (NPM) > Knowledgebase Internal > Install SolarWinds software and SolarWinds database (SQL Server) across a WAN

Install SolarWinds software and SolarWinds database (SQL Server) across a WAN

Table of contents

Updated September 26, 2018


If you install your SolarWinds software and SolarWinds database (SQL Server) across a WAN, ensure a reliable static connection between the primary region and all monitoring regions.


  • NPM 12.2 and earlier
  • Orion Platform products version 2017.3 and earlier


If you install your SQL Server and Orion server in different locations across a WAN, make sure that there is a reliable static connection between the primary region and all monitoring regions. This connection is continually transmitting monitoring data. The quantity of bandwidth consumed will depend on many factors, including the type and number of SolarWinds Orion Platform products that are installed, and the types and quantity of monitored elements.

Though it is possible to deploy your Orion server and Additional Polling Engines so that they connect across a WAN to your Orion database, SolarWinds cannot guarantee that your circuit can meet the I/O specifications, such as bandwidth, speed, and latency, to function properly. 

If distributed deployment is a requirement, SolarWinds recommends that you install the Orion Enterprise Operations Console (EOC) with multiple Orion instances at each distinct location across your WAN. See Orion EOC at for details.

Additional Polling Engines can cope with database outages, handle bad or slow connections, and work over WAN. Additional Polling Engines use Microsoft Message Queuing (MSMQ) to enable the local storage for up to 1 GB of polled data per polling engine to prevent data loss when the connection between the polling engine and the database is temporarily lost.







Last modified



Internal Use Only