nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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
Store

Move 2020.2.6 DB to SQL 2019

mato1964

Any considerations for moving a 2020.2.6 DB temporarily to SQL 2019 running Windows SQL 2019 OS?

Find more posts tagged with

Accepted answers

vinay.by

If you look at the SolarWinds requirements it does say you can run 2020.2.6 on 2019

https://documentation.solarwinds.com/en/success_center/npm/content/system_requirements/npm_2020-2-6_system_requirements.htm

But then as well NOTE that you are running a 'Unsupported version' (End of Life) and hence if the migration doesn't work as expected then you might not have any support from the vendor

__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT

All comments

vinay.by

If you look at the SolarWinds requirements it does say you can run 2020.2.6 on 2019

https://documentation.solarwinds.com/en/success_center/npm/content/system_requirements/npm_2020-2-6_system_requirements.htm

But then as well NOTE that you are running a 'Unsupported version' (End of Life) and hence if the migration doesn't work as expected then you might not have any support from the vendor

__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT__PRESENT

FormerMember

Why temporarily? What's the plan for the future?

mato1964

Customer wants to move databases ahead of the upgrade. It'll be:

*Move DB's to new server - rerun config wizard

*Migrate to new App server - run config wizard

mato1964

Awesome thanks - I should have seen this!

adam.beedell

Make sure the SQL DB recommended settings are the same, particularly the collation

Backup -> restore -> config wiz