1 of 1 people found this helpful
Do you have any nodes/volumes/interfaces on new database?
If not, you can simply point new NPM Configuration wizard to OLD database. It will create new tables etc. according your needs.
Backup OLD database before doing any action.
There is document, which can help you: http://www.solarwinds.com/documentation/Orion/docs/MovingYourOrionNPMDatabase.pdf
Be sure after run CW you have to check "Reassigning Nodes" part in above document, because 2 primary pollers are not allowed.
Thanks for the helpful response. I had considered doing this, but I don't want to keep any of the old data if I can get away with it. Mainly because the database is massive and full data for old/removed nodes.
I didn't realise that the config wizard creates missing tables! If, for example, the original server had NPM/NTA only, and the new one has many new modules but also includes NPM/NTA at the same version as the original, if I were to simply move the database and run the wizard against this old database as is, would it create the tables for NCM/VNQM/IPAM and so on?
This theory, if true, could save a lot of people a lot of time when it comes to migrations to new platforms.