| 437-991-3573 | Data Engineering Services
Resources Tools
Experts in Microsoft SQL Server on Windows, Linux, Containers | Clusters, Always On, FCI | Migrations, Cloud, Performance

The feature: "Scale-out deployment" is not supported in this edition of Reporting Services
by BF (Principal Consultant; Architecture; Engineering)

During a Migration Project for SQL Server Reporting Services 2014 STD to 2016 STD we ran into some errors with bringing online both the Report Manager and Report Server.


We were not able to browse the Report Manager and Report Server URL after we copied & restored the reporting services database from the 2014 instance to 2016 instance.


The feature: "Scale-out deployment" is not supported in this edition of Reporting Services


The reporting services database keys table had entries pertaining to older reporting services instance.


1. Upgraded Reporting Services 2016 to be the same version/build as the SQL Server 2016 version. (these are on separate servers)
2. Using the Reporting Services 2016 Configuration Tool, create the Report Databases as blank databases & test the report urls (just to test it works ok)
3. Backup 2014 Report Server Databases, Copy to the SQL Server 2016 server & Restore the two databases.
4. Delete from the KEYS table entries pertaining to old reporting services instance/servers. i.e. Select * from ReportServer$Dev.dbo.keys
(do this on the restored databases in Step 3)
5. Backup Encryption Keys, with password, from the 2014 SSRS.
6. Restore the Encryption Keys on the 2016 SSRS.
7. Test the Report Server and Report Manager now come online
8. Delete the blank SSRS databases that were created in Step 2.