December 22, 2020 at 1:46 am
We are going to upgrade Our SQL server and SSRS from 2017 to 2019.
This is going to be side-by-side upgrade. The hard part is we want to reuse the server name after migration. Also for this case db engine and SSRS service are on the same host, not separated.
It also means: to build a new server that hosts 2019 database engine and SSRS report service. then migrate db and reports, then rename the new server the same name of the old server. Old server will be renamed to something old then decomission after a week.
I plan to do in these steps, the challenge part is when we want to swap and reuse the servername.
2. Backup the old report databases and encryption key on old server MyServer ,stop SSRS service there and restore on the new server.
3. do reporting server configuration and restore encryption key on new server
It is possible that I got a scale out error, I may need to go to key table to delete the key of original server.
4. Test reports
5. Swap OS server name,rename MyServer to ServerC and Rename ServerA to MyServer.
Below is something I plan do do, but not sure if it is right way or best way, please help
6. On the old server, I will go to db engine using sp_drop sever and sp_add server to change the SQl sever name, then reconnect database to ServerC. Do I need to restore encryption key again or not since I am on the same sever?
7. On the new server, I rename the SQL server name from its original name ServerB to Myserver using sp_dropserver and sp_add_server....and reconnect the datatabase from report configuration manager, do I need to restore encryption key again?
Is there going to be another SSRS instance showing up in key table?
December 23, 2020 at 2:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply