February 21, 2019 at 10:47 am
I hope someone can verify this for me.
We're about to upgrade to 2017 and we're addressing an old question that is apparently causing issues in our current 2012 environment.
Set up would be 4-node cluster, cross-datacenter with 2 servers on each DC. On each DC, one server would be OLTP and the other would be reporting. I've read that we can add the regular report server db to an AG without needing to add the tempdb version (correct me if I'm wrong). But what we want is to add a load balancer to the mix.
Load balancer (vip) -> web servers -> database instance where SSRS is installed. If we have a listener on the web servers redirecting to the SSRS database, is that the same has having a running SSRS service on those servers?
If not like running the SSRS service (which does require an extra license), is the listener something we have to pay an extra license fee for?
My network / hardware knowledge is a bit out of date, so I'm crash-coursing this info as fast as I can. Any assistance (links, explanations) you can give me would be appreciated.
February 22, 2019 at 12:17 am
I've read that we can add the regular report server db to an AG without needing to add the tempdb version (correct me if I'm wrong). But what we want is to add a load balancer to the mix.
If you do this, then you will need to restart SSRS after AG failover to recreate the TempDB database. Easier to just add it to the AG, this usually has minimal impact and simplifies failover.
Load balancer (vipvip) -> web servers -> database instance where SSRS is installed. If we have a listener on the web servers redirecting to the SSRS database, is that the same has havinghaving a running SSRS service on those servers?
If not like running the SSRS service (which does require an extra license), is the listener something we have to pay an extra license fee for?
No, the listener is not the same as having multiple SSRS instances. Ultimately, the load balancer and web servers are going to point to a single SSRS instance, which may end up being a bottleneck, but from a licensing perspective means you only need to pay for that instance.
As with any licensing question though, the safest bet is to check with your licensing reseller for confirmation.
February 22, 2019 at 4:23 am
Thank you. I appreciate the information. I was wondering about that temp database thing. Someone on another thread / another website (I can't find the link right now) had said it didn't need to be in sync on the different nodes and that just rubbed me the wrong way.
February 24, 2019 at 9:26 am
Brandie Tarvin - Friday, February 22, 2019 4:23 AMThank you. I appreciate the information. I was wondering about that temp database thing. Someone on another thread / another website (I can't find the link right now) had said it didn't need to be in sync on the different nodes and that just rubbed me the wrong way.
Load balancing SSRS is scale-out and is an Enterprise only feature. You can install multiple instances of the SSRS service and configure each instance to point to a single database hosting the report server databases.
Each 'web server' will need to be licensed.
Also - since SSRS is not AlwaysOn aware - the service(s) on the 'web servers' needs to be restarted if the group is moved to the other server. See this article: https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/reporting-services-with-always-on-availability-groups-sql-server?view=sql-server-2017
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
February 25, 2019 at 4:39 am
Jeffrey Williams 3188 - Sunday, February 24, 2019 9:26 AMBrandie Tarvin - Friday, February 22, 2019 4:23 AMThank you. I appreciate the information. I was wondering about that temp database thing. Someone on another thread / another website (I can't find the link right now) had said it didn't need to be in sync on the different nodes and that just rubbed me the wrong way.Load balancing SSRS is scale-out and is an Enterprise only feature. You can install multiple instances of the SSRS service and configure each instance to point to a single database hosting the report server databases.
Each 'web server' will need to be licensed.
Also - since SSRS is not AlwaysOn aware - the service(s) on the 'web servers' needs to be restarted if the group is moved to the other server. See this article: https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/reporting-services-with-always-on-availability-groups-sql-server?view=sql-server-2017
We don't load balance SSRS specifically, if I understand what I've been told. But I'm adding your comments to our notes so we can verify what we're doing on the next build.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply