March 17, 2015 at 2:25 pm
I do have an separate SSRS server and 3 node A/A/Active cluster db server. I kept the 2 report databases in the DB server. Is this the standard approach. Will this work in event of failover (yes, SSRS is not cluster aware). Or should i keep the 2 report databases in the SSRS server?
March 17, 2015 at 2:51 pm
I don't know what the "standard" way to do it is, but we are looking into a similar scenario with our upcoming AlwaysOn implementation.
What I think I'm going to end up doing is having two database servers at different sites involved in the cluster, and have everything but the SSRS databases in the DAG. Then have a web server with SSRS installed on it at each site pointing to the SSRS databases on the DB server at their site.
Not sure if it's really the preferred way, but I don't see that it has any major disadvantages.
The Redneck DBA
March 18, 2015 at 4:29 am
balasach82 (3/17/2015)
I do have an separate SSRS server and 3 node A/A/Active cluster db server. I kept the 2 report databases in the DB server. Is this the standard approach. Will this work in event of failover (yes, SSRS is not cluster aware). Or should i keep the 2 report databases in the SSRS server?
It's perfectly valid and acceptable to put the report server databases onto a highly available failover cluster instance of sql server. This does of course increase your licencing footprint by separating an SSRS instance out from the database engine.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 18, 2015 at 2:57 pm
We have our SSRS DBs in an A/A configuration and they work well. The only gripe I have about it is the nasty SQL Agent jobs that SSRS report subscriptions makes. Gives me a headache just looking at the job list on that server.
We also have another instance with SSRS DBs in an AG, something I personally hate and I am removing. The DBs fail over just fine in the AG. The pain point comes in the subscriptions and agent jobs. If you want everything to work after you fail over you have to make sure you manually/script all jobs created on the one server to all other secondaries. Then if you don't want duplicate subscriptions running you have to either write a script to disable the jobs or add a step to every job to check if it is the primary server and if so then execute said job.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply