Anyone ever upgrade from 2020.2 to 2025.1

We went from 2020.x to 2024.x and then to 2025.1. We've had nothing but problems and followed the upgrade docs to ensure all ports needed were open and whatnot. But having major slowness. Getting database blocks from NPM that we cannot figure out. Have Solarwinds helping and they haven't been able to narrow it down either. We do have some monitors that are still in an unknown state after the upgrade, such as ones using perl scripts.

Just thought I'd check and see if anyone has had a similar experience at all. Thanks!

Find more posts tagged with

Accepted answers

All comments

Lofstrand

I have seen issues on the SQL side before after upgrade/migrations. A restart of SQL helped then. (if you can't figure out what thread that created the issues.)

flexharm23

I went through a similar upgrade path from 2020.2 up to 2025.1 and also faced major slowness, random database blocking from NPM, and several monitors stuck in unknown states (especially custom perl-based ones), so you’re not alone—SolarWinds support helped us tweak some SQL maintenance jobs and optimize polling engines, which reduced the blocking, but it’s still not as smooth as the older version; one thing I’d suggest is checking your polling engine distribution and database growth closely since upgrades often leave behind legacy table bloat, and while it’s frustrating, think of it like playing pile ou face google—sometimes you get a stable upgrade, sometimes you end up troubleshooting for weeks.