Do you have a comment or suggestion to improve SQL Server? We’d love to hear it!

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.

Best Regards,
James Fuller
James.fuller@amwins.com

137 votes
Sign in
(thinking…)
Password icon
Signed in as (Sign out)

We’ll send you updates on this idea

James Fuller shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

24 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • John Zabroski commented  ·   ·  Flag as inappropriate

    Hi,

    I believe I have discovered an alternative path forward today: Docker containers.

    The following article explains how to use Docker containers to create multiple SSRS instances on the same machine: http://www.sqlservercentral.com/articles/containers/178448/ - In theory, all you need to do is bind the exposed port for SSRS to a unique port for each container instance.

    I had stumbled upon this answer today while trying to figure out how to create repeatable test environment for Microsoft's Powershell Module ReportingServicesTools, and it occurred to me this would be a cheap way to also do multiple instances of SSRS on the same machine.

    NOTE: I have not yet tested this, just sharing my clever idea with everyone.

  • Barry McCauley commented  ·   ·  Flag as inappropriate

    Just reployed 3x SQL 2017 instances, before finding this out.

    Now destroying them and rebuilding as 2016. Blocking use of SQL2017 across the business now.
    Why, Microsoft, why?
    *shakes fist at the sky*

  • Juan Manuel Ramirez commented  ·   ·  Flag as inappropriate

    We use multiple instance feature in previous versions of SQL Server, we're unable to upgrade to SQL Reporting Services 2017.

    Please restore this feature...

  • Anonymous commented  ·   ·  Flag as inappropriate

    Add my voice to this.
    Not allowing multiple instances in reporting services has prevented a number of my data center customers from upgrading to SQL Server 2017.
    Discouraging customers from upgrading is not a great Microsoft idea.

  • Anonymous commented  ·   ·  Flag as inappropriate

    So will M$ compensate us now for the additional VM's we have to spin up ?
    Who the.. came up with this idea ? Please add it back asap!

  • Anonymous commented  ·   ·  Flag as inappropriate

    We have several databases running inside our sql instance in the app when we change the database connection and call to the report server instance, we change the report server instance that we call to depending on the database our app is looking at. On 2016 we installed a different SSRS instance with all the report databases pointing to the correct report databases and app data.
    We need this restored. Thanks

  • John Zabroski commented  ·   ·  Flag as inappropriate

    I think I'll just push us to us AWS bi tools if this is how Microsoft wants to treat customers.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Bad design. Needs to recheck. Multi instance SSRS is required otherwise I'd have to spin up extra VMs just for SSRS. Not ideal.

  • Shawn C commented  ·   ·  Flag as inappropriate

    Under review on "Feb 5, 2018"? Today is Nov 21st 2018.

    What do you expect us to do with SSRS? Stop using it? Use if for free?

  • Shawn C commented  ·   ·  Flag as inappropriate

    1. This blocks my deployment of SQL Server 2017 database engine. I need SSRS to be the same version for some apps.
    2. I require total isolation of SSRS instances for security

    I assume it's now free to use and I can install anywhere I want with no cost, on all the indivudal app servers instead of a shared BI servers?

  • Sergio Sanz commented  ·   ·  Flag as inappropriate

    Please do what all my predecessors (and my self) are asking for.
    I'm administering hundreds of customer's SQL instances in 2008R2-2016 versions, and quite of them are SSRS servers installed in scale out pattern (behind a load balancer) with the same SSRS instances installed on every server.
    This allows to have different ports, configuration, administering, etc for every set of instances, serving to one application.
    With this new one-instance SSRS model we will not be able anymore to do so. Our clients are looking for other options.
    Thank you.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Please restore this functionality. It is critical for our testing and deployment environments.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Please restore this functionality. It is critical for our testing and deployment environments.

  • Anonymous commented  ·   ·  Flag as inappropriate

    +1. This was one of the differentiating features of SSRS compared to competing products. If it stays single-instance it will force my company to reevaluate SSRS as a solution.

  • Jeff commented  ·   ·  Flag as inappropriate

    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.

  • Anonymous commented  ·   ·  Flag as inappropriate

    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, ...).

← Previous 1

Feedback and Knowledge Base