Installing Reporting Server for "fail-over" operation

  • Has anybody setup Reporting Server for fail-over?  My client has done this and I have yet to get an explanation or demonstration.  The visible part is that there are two additional databases in the instance.  The standard "ReportServer" and "ReportServerTempDB" are present; bu there are two additional databases named "ReportServer_AppXX" and "ReportServer_AppXXTempDB" - where XX = the host name of the failed server.  On the failed server there are also two additional DBs that point to this server.

    How they are used is still a bit of a mystery to me.

    Can anybody point me to a document that describe the how and whys of this configuration?  I would like to figure it out before someone has to tell me... and since I am also in the process of setting up replication on these servers, it would be awfully nice to understand what is going on so I don't break anything.

    Comments?

    Thank-you,
    David Russell
    Any Cloud, Any Database, Oracle since 1982

  • Turns out that this is a very clever configuration to allow Standard Edition to be installed in a cluster configuration.  According to Microsoft in order to implement a "scale-out" configuration you must use the Enterprise Edition at four times the cost.

    I would be awfully interested to hear if anyone has installed Standard Edition (Reporting Server) in a cluster.  Let me know if you'd like to know the details, and perhaps I will attempt an article for Server Central.

    Thank-you,
    David Russell
    Any Cloud, Any Database, Oracle since 1982

Viewing 2 posts - 1 through 1 (of 1 total)

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