Network Management

Merge data/tables from one SolarWinds Platform database to another

This article discusses the idea of merging data/tables from one SolarWinds Platform database to another.

First published date

10/25/2018 7:04 PM

Last published date

9/18/2025 2:12 AM

Overview

It is quite common to receive requests about merging two SolarWinds Platform databases. Here are some situations where this kind of request comes up:

  • When a company running a SolarWinds Platform deployment acquires another company that also runs an existing deployment).
  • An attempt to restore data from an old corrupted database to a new one
  • New SolarWinds Platform database created as a result of migration/upgrade related issues

Product section

Network Performance Monitor

Cause

Each SolarWinds Platform instance has its own SQL Server and database, and the database cannot be merged into one.

Resolution

The SolarWinds Platform does not support the merging of Two complete SolarWinds Platform instances into one system. Each SolarWinds Platform instance has its own SQL Server and database and the database cannot be merged into one.

Workaround:
The only alternate way we can think of is to use one of the SolarWinds Platform instances then run network discoveries on the nodes of the "other" SolarWinds Platform instance. Unfortunately, the newly added nodes will not include historical data and the devices from the "other" SolarWinds Platform instance will need to be configured to be polled by your chosen Main SolarWinds Platform instance.

If you need historical data, then it is best to leave both SolarWinds Platform instances polling their own set of Nodes.

Running Network Discovery:
Discover your network for the SolarWinds Platform with the Discovery wizard
​​​​​​