Upgrade Path from SolarWinds Product Advisor and Need Suggestions

Q1:
As long as the Database is SQL2016 you are good to go for now. SQL Server OS is not that big of a concern.

keep in mind, that you eventually need to upgrade that as well. But moving the Database is no big deal. I am personally not a fan of in place upgrades, but I have done those as well.

Q2:

there are some documents on virtual environments, I need to dig a little

Q3:

have your database maintenance running, have a DBA take a look at the server from time to time

hope that helps

Thanks HerrDoktor​ for your very well explained answers of my questions, and yes database maintenance are running and also DBA look at the server from time to time.

What i wonder, we have also an option to migrate our current DB instance to a new physical machine running server 2016. So if we migrate to the new one, what are the sizing requirements for this process.and do you know with this enviroment, roughly how much is the down time would be required?

And last option, it also could be Physical 2 Virtual (P2V) migration of our DB server, currently understood this is not advised due to the high IO workload of SolarWinds. If possible, if you could send me any documentation about this option as well.

Thanks

Llike mentioned earlier, I would do this in a separate task. When migrating Databases I usually do a Backup/Restore procedure.

in your case:

- stop all Orion related services on MPE/APE

- back up your Orion Database(s) and make a snapshot of your current MPE/APE

- take those DBs offline, so you know when something with the redirects is not going as expected.

- copy the DB BAK files to your new SQL Box and restore the Databases

- check if you have any tasks/Maintenace Plans running on your Old SQL that you need to copy over

- start the Config wizard on your MPE and point to the new SQL Server in the Conf-Wiz menu.
- Let the config wizard create your SWDB users for you, those will have the correct permissions then.- start config wizard on your APE, point to the new SQL Server like on your MPE, letting the wizard create the SWDB users

- test your system

that should be it

Downtime really depends how fast you can copy over the BAK files and restore them. Config wizard should be done in 10 Minutes depending on the Database size.

sizing requirements also depend on multiple factors.

- polling intervals

- retention time

- number of systems/nodes

- number of monitors (application etc.)

as for CPU/Memory for the SQL ... the more the merrier

Thanks a lot, Dear HerrDoktor​. Your feedback and expert review will help me, and just for curiosity, if later you will find something relevant to P2V migration documentation then please forward me.

Thanks

Thanks a lot, Dear HerrDoktor​. Your feedback and expert review will help me, and just for curiosity, if later you will find something relevant to P2V migration documentation then please forward me.

Thanks