Microsoft Reporting Server SSRS 2012 Architecture

1
votes

We are planning to deploy reporting service using Microsoft Reporting Server 2012. As I understand it, there will be three components;

  1. Database (SQL Server)
  2. SSRS (Reporting Server)
  3. IIS (Web front end) - SharePoint (alternate Front end)

In setting up the Proof-of-Concept, the dev installed SSRS and SQL Server on same box (let's call it the DB server) and is redirecting client browser to a URL on DB Server from web front end.

Is it possible to architect the solution so that the web front end is the only destination for client browsers, SSRS lives on its own dedicated server separate from both the Web server and the DB Server?

How will authentication work in this scenario? We are using integrated authentication using Enterprise AD.

1
reporting-servicesssrs-2008ssrs-2008-r2ssrs-2012

1 Answers

2
votes

Configurations I have used in the past are these:

  1. SQL Server on one server; SSRS native on another server. Users accessed reports via the SSRS Report Manager web UI that comes with SSRS.
  2. SQL Server on one server; SSRS install in SharePoint Hosting mode on another server. Users accessed reports via SharePoint.

I am not 100% sure what you mean by “web front end is the only destination for client browsers”. If you mean that the end user only hits a web server, and not the database server to get reports, then either one of the above will work. If you have an existing intranet site that you want to host reports in, you can do so via web parts, if you are using MS technologies. You will still need SSRS setup somewhere so you can deploy reports, and the web part would read from it. Or, you can continue the redirect to either Report Manager or SharePoint if you go that route.

As far as authentication: the authentication between SSRS and SQL Server is usually done via an AD (Active Directory) user/service account that SSRS runs under, and also has access to the databases is uses on the SQL Server.

The authentication that allows users to browse and execute reports is usually done via AD as well. You can add all users to a central AD group and give that group Browser permissions on the SSRS server. This authentication would still apply if you use web parts to host reports outside of SSRS Report Manager.

The authentication that SSRS uses to pull the data that ends up showing in reports is usually SQL Server authentication, or whatever authentication that your data source supports where you can send a user name and password (which is stored within a shares data source on SSRS).

More Info