Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Database schema of 2017.3 vs 2020.2.6 prior to migration to 2022.4.1

We are about to build a totally new 2022.4.1 Orion Platform instance for various reasons that I will not discuss here.

However, we will be referencing an existing 2017.3 instance in parallel. We will of course be copying/importing various content such as alerts, reports, app templates, custom properties, etc as needed.

My question is this, would it be beneficial to upgrade the 2017 instance to 2020.2.6 BEFORE doing any migration/importing of custom content? Would doing so lessen the chance that database schema differences would "break" some things?

Find more posts tagged with

Accepted answers

All comments

stuartd

Interesting question, and one I don't know the answer to.

But let me suggest here: https://thwack.solarwinds.com/product-forums/the-orion-platform/f/orion-sdk might get more traction as that is where some of the API guys hang out and as they deal with the DB schema for fun may have a more solid answer. That or tech support (yeah, right! )