SQL Always On for report services

Salves 501 Reputation points
2020-10-08T12:04:05.19+00:00

Hi,

in my searches I found that the report server should not be used in scenarios with SQL Always On, as some information is specific to the report services and even if replicated to another server it will not work.

To work it is necessary to make a series of changes for the replicated database to work.

What is your opinion?

I installed the report server on the three servers and now what do I have to do?

Thank you.

SQL Server on Azure Virtual Machines
SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,640 questions
SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
2,790 questions
0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Leon Laude 85,646 Reputation points
    2020-10-08T12:15:03.747+00:00

    Hi @Salves ,

    I suggest you go through the official Microsoft documentation below:

    Reporting Services with Always On Availability Groups (SQL Server)
    https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/reporting-services-with-always-on-availability-groups-sql-server?view=sql-server-ver15

    ----------

    (If the reply was helpful please don't forget to upvote or accept as answer, thank you)

    Best regards,
    Leon

  2. AmeliaGu-MSFT 13,961 Reputation points Microsoft Vendor
    2020-10-09T02:36:09.197+00:00

    Hi @Salves ,

    Please refer to this tutorial which might help.

    Best Regards,
    Amelia

    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  3. AmeliaGu-MSFT 13,961 Reputation points Microsoft Vendor
    2020-10-09T02:36:09.393+00:00

    Hi @Salves ,

    Please refer to this tutorial which might help.

    Best Regards,
    Amelia

    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  4. Ben Miller (DBAduck) 951 Reputation points
    2020-10-11T01:33:41.667+00:00

    The reality of Reporting Services and AlwaysOn Availability Groups, is that Reporting Services lives on a server and points to a writable copy of ReportServer database. Having the ReportServer database in the AG gives it the ability to failover to the secondaries. The other reality is that the secondary cannot be written to, so you really cannot point the Reporting Services to the secondary to write.

    So the option you have is to point the Reporting Services to the AG Listener so that if the AG fails over the Reporting Services still continue to work and keeps it highly available. The challenge will be if you reboot the Primary Server the reporting services will stop until it is rebooted completely. You could do a scaleout Reporting Services implementation if you wanted to.

    Only the databases that are used in reports can use ApplicationIntent=ReadOnly in the connection string to leverage the readable secondaries.

    0 comments
  5. growth360 81 Reputation points
    2020-11-11T04:10:15.537+00:00

    We use the SQL Always On for Conversion Rate Optimization and real-time personalization services. We point the Reporting Services to the AG listener so that it works properly!

    0 comments