Restore multiple instance support for Reporting services in SQL 2017
Please restore the multiple instance support per server for Reporting Services 2017. SQL Server reporting Services has supported multiple instances on one server in versions SQL 2000 thru 2016 and it was removed by design with the release of SQL 2017. This was a bad move as it will force my company to deploy 6X as many servers to deploy what is a lightweight application server.
I'm not sure if this has anything to do with the PowerBI integration with SSRS, but it also suffers from this bad decision as well.
This will cause my company to consider a different reporting tool. We are doing a new system implementation starting from scratch and we picked SQL Server 2017 because it was the latest and greatest, but this has stopped us in our tracks.
Paul Ross commented
Why? Give it back!
For us this is show-stopper for upgrade to SQL Server 2017. Our customers use SSRS named instances for separation of projects and for separation of environments (TEST, PROD, ...).
We use multiple instances of SSRS on the same server to isolate our test from production and for applications that require a specific version/patch level of SSRS.
Peter Row commented
You chucked us under a bus when you change the way things work when implementing a custom security DLL if we need non-Windows auth. Now I come to investigate that problem and find you've pulled this stunt, unbelievable!!!!!!!!!
Add it back now, no please, just ******** do! So angry right now.
Javier Villegas commented
It is really important to have this functionality back as it was before
Please add this back in. We run many instances of SSRS 2016 on one server in a test environment. I really don't want to create a VM for each instance especially with as light of load as ssrs has during testing.