I have a requirement of migrating my whole SQL Server from SQL Server 2012 to 2016. I have already migrated the database engine part. Since I have not really worked on SSRS (reporting part), so need some immediate help.
Following steps I will be taking:
- I have to backup and restore the ReportServer database and ReportServerTempDB
- I have to backup and restore the encryption keys
- I will congifure SSRS through Reporting Server Configuration Manager
What else steps should I be doing to be able to run the reports here on SQL 2016 same as it used to run on the server for SQL 2012. I have heard we have to manually copy so RDL files to new server etc.
Kindly help!
Best Answer
Try RSMigrationTool.exe and RSMigrationUI.exe from Microsoft
Here's a brief excerpt from the white paper link I included below, together with the migration tool download URL and Backup/Restore Encryption Key URL:
Export the SSRS items by using the RSMigrationTool.exe.
a. Open a command prompt as an administrator.
b. Navigate to the folder that contains the extracted RSMigrationTool.exe.
c. Run the tool with the following parameters.
RSMigrationTool.exe [-n native_report_server_url] –I native_report_server_instance [-h] –f migration_metadata_files_folder [-p password]
White Paper
http://download.microsoft.com/download/D/2/0/D20E1C5F-72EA-4505-9F26-FEF9550EFD44/MigratingContentBetweenReportServers.docx
Migration Tool
https://www.microsoft.com/en-us/download/details.aspx?id=29560
Backup and Restore Encryption Keys
https://docs.microsoft.com/en-us/sql/reporting-services/install-windows/ssrs-encryption-keys-back-up-and-restore-encryption-keys?view=sql-server-2017
Alternately try restoring the SSRS databases
And, if you want to go that route, you can try to restore the SSRS ReportServer and ReportServerTempDB databases to the target server. This example shows moving from SQL 2005 to 2008 SSRS:
https://docs.microsoft.com/en-us/sql/reporting-services/install-windows/ssrs-encryption-keys-back-up-and-restore-encryption-keys?view=sql-server-2017
As always, try all these things on a test/dev SQL Server first.