In this article, I will explain
How to Scale-Out SQL Reporting Service (SSRS) deployment (Always-on)?
I have 2-Tire SharePoint Farm
- 1 WFE + 1 APP Servers.
- 2 Database Servers (Always-on).
- Reporting Service Native Mode.
Note: If you need to use Reporting Services with SharePoint. it’s recommanded to configure SSRS SharePoint integrated mode with Reporting service application service on an indpenedent reporting server to ensure the Performance, Manageability and Security.
But in my case, the customer budget is not enough to apply the best practice, Meanwhile configuring SSRS SharePoint integrated mode with Reporting service application service on the same WFE + APP server lead to low performance.
So I have decided to work with SSRS Native mode to ensure at least the performance and show reports inside SharePoint via:
- Report Viewer Web Part.
- View / Explore SSRS Native Mode Report via PerformancePoint within SharePoint
And in this case, I should configure SSRS Native mode on both SharePoint WFE Servers because as we know the Database Servers are not accessible over the internet,
Note: If you configured SSRS native mode on only one WFE server. you will get it worked properly. but sometimes when browsing the Report Manager URL you will get 404 error!
This error occurs when the load balancer hit the second WFE node (where SSRS is not installed), so the directory of reporting service will not be found and you will get
404 file or directory not found.
On the other side, when the load balancer hit the first WFE node (where SSRS already installed) the Report Manager URL will work without issue.
So you should configure SSRS on the second SharePoint WFE node by scaling out SSRS deployment to share the same single Report Server Database.
Note: In this article, I considered you already have installed and configured the SSRS in the first node by following the mentioned instruction at Install and Configure SQL Server Reporting Service (SSRS).