It's possible, yes, but scalable not in the manner we would expect.
Depending on your resources, you may find one of these other solutions a better approach:
Use Access Database with a neat GUI that connects to your server table read/write for almost real time changes ~ then use SSRS to build reporting around the data.
Use SSIS package to pick up excel ...
Because the ReportServer and ReportServerTempDB databases need to be able to communicate with each other, SQL Database is not a valid option.
However, if you migrate to SQL Server 2008 in an Azure VM and have Software Assurance then you may be able to get extended support and continue to use the 2008 version for an extended period.
why would that be the case only with SSRS?
As addition note to the Handy's answer, one of the main reason, SSRS dependencies are not only in ReportServer and ReportServerTempDB databases, but also on SQL Server Agent which host all the subscription configuration of the SSRS and which would not be a scope of AG replication.
So, you got covered ReportServer ...
The reason the documentation states that automatic failover is not supported is that there are post-failover tasks that must be carried out to ensure the Report Server is completely online. See this section for information on exactly what tasks need to be completed. Essentially it boils down to needing to stop the SQL Agent on the old primary and restart the ...
I assume you are talking about migrating ReportServer and ReportServerTempDB. As per this document, Azure SQL Database is not supported. Below are the support databases
Azure SQL Managed Instance
SQL Server 2019
SQL Server 2017
SQL Server 2016 (13.x)
SQL Server 2014 (12.x)
SQL Server 2012 (11.x)
SQL Server 2008 R2
I have done one Reporting Server ...
After some digging I found plenty of unconnected issues, but finally managed to solve them and wanted to share them all in one place so nobody else waste that much time if hits the same issue (or some of them).
First you want to access is the Reporting Services Error Catalog, depending on your installation directory, it will be something like this:
The answer is in your first link:
DatabaseQueryTimeout - Specifies the number of seconds after which a connection to the report server database times out.
This setting only applies to the connections from the RS services to the RS databases, not for individual reports to their data sources. This makes sense given:
This value is passed to the System....