'SQL Server Reporting Service (SSRS) on Azure SQL Database [closed]
Azure SQL Database supports Full recovery model and we can't change the recovery model of Azure SQL Databases.
As mentioned here while making report server all application data is stored in reportserver and reportservertempdb.
According to the specific recommendations reportserver follows full recovery model and reportservertempdb follows simple recovery model.
So is it only the reason that reportservertempdb follows simple recovery model and that is not supported by Azure SQL database we can't configure SSRS on Azure SQL Database or there is something else too.
Please help me out with this with docs or links.
Solution 1:[1]
Azure SQL single database doesn't support SSRS. And Azure SQL database product team said they have no plan to add it.
You can continue configure the SSRS for Azure SQL managed instance or use if for SQL Server in VMs.
Ref this feedback:
Solution 2:[2]
This is a confusing topic because it makes sense that Azure SQL db architecture and development team would not support running SSRS front end and site as it requires IIS, and all the infrastructure. The accepted answer has a link that is no longer valid. The issue is that the question and answer do not specify what is and what is not supported- is it just the front end? Can the databases be hosted in Azure SQL and front end on a VM? It's not a complete question, or a complete answer. User says they want SSRS on Azure SQL but how was that interpreted and how did the MSFT read that question, and why was the response not detailed at all?
Another poorly written suggestion remains unanswered from 5 years ago, and I think it's the reason for the quick undetailed response from MSFT, because they get a lot of these that dont make sense: https://feedback.azure.com/d365community/idea/53567a64-7b25-ec11-b6e6-000d3a4f0da0
As I read it, OP is asking if this can be done in a hybrid method (this is separate completely from expecting SSRS site to run in a database alone), where the front end is on a VM and backend is in Azure SQL. The only limitation found is a recovery model discrepancy. I think that full recovery model might be fine to run. There are other SO post saying it has been done as hybrid deployment:
When we read the differences between simple and full recovery model on a database, full has logging and simple does not. Applying logging where it's not needed does not seem like it would break anything: https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/recovery-models-sql-server?view=sql-server-ver15
My answer would be, have you tried it and received an actual error? Try it and see. I'm up against the same problem now and researching before setup. I am checking with my DBA team shortly and may proceed with a hybrid configuration. If I do, I will try to remember to follow up with my result.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
Solution | Source |
---|---|
Solution 1 | TylerH |
Solution 2 |