Clustering Reporting Services

  • Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/zmattson/clusteringreportingservices.asp

    Cheers
    http://twitter.com/widba
    http://widba.blogspot.com/

  • Have you done anything with say the Report Server web service being a middle tier and Windows integrated security being used throughout?

    K. Brian Kelley
    @kbriankelley

  • We have set it up in a dev environment with the RS service being a middle tier.  We used Windows security for the App->RS Server security but kept the database connection to a database user to keep things simple in our environment. 

    Thanks. 

    Cheers
    http://twitter.com/widba
    http://widba.blogspot.com/

  • This is a great article and explains the installation process very clearly.

    Our cluster is a multiple instance (active/active) cluster with the first node being the production instance and the second being the beta instance. Our beta instance will not be very busy. If we wanted to install RS in a two node active/active cluster, would we perform the same steps on both nodes? Since RS is resource intensive are we asking for trouble running it on the production instance or would it be best to just run it on the Beta instance?

    Thanks!


    Wendy Schuman

  • Hello Zack,

    Just ran into your article. I'm trying to research setting up Reporting Services on a SQL cluster from the licensing perspective, and have not found any good information on the subject. Does running SSRS on both nodes of the cluster (active/passive) require the passive node to be licensed? Also, the configuration you've set up I believe is supported only in Enterprise Edition, not Standard Edition?

    Thanks!

    Randy

  • Hi Zack--

    I know this is an old article, but it sounds like exactly what I have been looking for. Is there any reason this would not work using SQL Server 2008 R2?

    Thanks,

    Tony

  • tferrara (1/27/2012)


    Hi Zack--

    I know this is an old article, but it sounds like exactly what I have been looking for. Is there any reason this would not work using SQL Server 2008 R2?

    Nearly 3 years since the last comment, yeah, old..

    1. IIS is not needed for SSRS as of SQL 2008 (and R2)

    2. This is considered a scale-out deployment and is only supported on Enterprise Edition as far as I know.

    3. As the last poster commented as a question about licensing, both nodes would have to be licensed, which would not be an issue in the Active/Active case since you would need to license both anyway.

    4. Technically SSRS is not cluster aware so it will not failover in any traditional sense. You are really only effectively running two copies.

    CEWII

  • Thanks for your reply, Elliott. I wanted to be sure there were no gotchas lurking before I recommended this.

    All four of your points are certainly correct. As for the licensing, though, this configuration is certainly more frugal than the other scale-out configurations that I have found. It lacks a public-facing server, of course, but it provides high availability inside our firewall, which is what I've been looking for.

  • tferrara (1/30/2012)


    Thanks for your reply, Elliott. I wanted to be sure there were no gotchas lurking before I recommended this.

    All four of your points are certainly correct. As for the licensing, though, this configuration is certainly more frugal than the other scale-out configurations that I have found. It lacks a public-facing server, of course, but it provides high availability inside our firewall, which is what I've been looking for.

    Provided the hardware is robust enough it is a workable model and cost effective. And Scale-out can be quite expensive. Since you have 2 separate SSRS servers you might consider putting a load balancer in front of them to control the loads..

    CEWII

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply