Good Afternoon -
We are planning on moving our DPA SQL DB to a new server off the current Solarwinds SQL server to its own dedicated SQL server. I found this article and plan on following it - Move a DPA repository on SQL Server - SolarWinds Worldwide, LLC. Help and Support but just wondering if there are any other things that I it might miss? I am going from Server 2016 SQL 2017 to Server 2016 SQL 2017. Thanks - Dave
First of all, it's great you found the success center article!
Seems like your environment is pretty straight forward. Just a few things to remember:
8 )
Everything should work great per the instructions. With a backup though, in case anything does go south, support will be able to help guide you.
Oh yeah. Early on in my IT career I did not take a backup or a snapshot when I could. You usually only do that once.
The only thing I think that should be perhaps added to the article and can be a gotcha is if you are using SQL server authentication. The step that has you add a login on the new server does say to match the credentials to the old server. This is correct but, with SQL server authentication if you create a login on one server and then create a login on a new server the Security Identifier (commonly abbreviated SID) can be different so it doesn't map to the user that is in the database on the restore.
If you use windows authentication for the connection the SID comes from the domain so it isn't an issue. If you are using SQL authentication a better step can be to create the login with a script to sync the SID from the old server. There is a really good blog post on it here.
https://blog.sqlauthority.com/2015/04/18/sql-server-create-login-with-sid-way-to-synchronize-logins-on-secondary-server/
Also if you have issues do just reach out to open a support case.
Great point!
