October 30, 2020 at 3:59 pm
This is a little awkward to explain, but we have 2 SQL Server instances that have a Standard license. Based on this article, it is entirely possible to setup availability groups for the SSRS DB's (ReportServer and ReportServerTempDB) The author of that article clearly uses Enterprise since hes got two DBs in one availability group. Well, I was able to successfully setup basic availability groups of the two DBs. I created one listener that is entered in as the instance that SSRS uses for the web portal on both servers. On the primary, I can navigate to the report URL while using the listener i.e. (http://listener/reports)
After working through some other issues, I thought I had the secondary server setup correctly. I failed over the DBs to it and am now stuck: The local URL (http://Replica2/reports) reports this: "The feature: "Scale-out deployment" is not supported in this edition of Reporting Services. (rsOperationNotSupported)" when using the local SSRS DBs.
Ugh. Is this a dead end? I guess because the DB's are part of an availability group, Microsoft sees it as one DB and thus our standard license prevents us from having two report servers even though their DB's are local to them?
October 31, 2020 at 4:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
November 10, 2020 at 3:26 am
This was removed by the editor as SPAM
November 10, 2020 at 9:42 am
You can't scale out in standard edition.
The link you refer to has enterprise SQL as they are adding 2 databases to 1 AG which is an Enterprise only feature.
With Standard its BAG's which is 1 database to 1AG so configuring SSRS to have two different DSN's is not possible.
It can be done if you have the ability to network load balance and some other method of doing the database syncs, but you cannot do it in Availability Groups
But as SSRS is not cluster aware if you install SSRS on 2 or more servers you need to license all servers so make sure you have enough licenses before you even think about doing that.
November 10, 2020 at 8:00 pm
You cannot utilize the Enterprise scale-out feature on a Standard instance - but, there is nothing that I am aware of that requires the databases to be hosted on Enterprise Edition.
With that said - you should be able to setup and license 2 web/app servers with minimal CPUs (2 2 core processors = 2 Enterprise Core licenses, per web/app server). This would be much less expensive than licensing the database server.
You can then host the databases on the Standard Edition and utilize scale-out deployment on the web/app servers. I would not setup the databases in a BAG though...instead I would setup a normal FCI cluster to handle failover and HA for that instance. The problem with using a BAG is that SSRS has 2 databases and both need to be failed over at the same time and a BAG is only one database.
Frankly - if you have enough traffic on your reporting servers to require a scale-out solution then paying for Enterprise Edition on the web/app servers shouldn't be an issue. The cost is well worth the benefit of load-balancing the reporting...
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
November 10, 2020 at 8:02 pm
And...the added features that are available in Enterprise Edition would also be well worth the extra cost. Data-driven subscriptions would be a large advantage to reporting solutions.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply