locked
Reporting server integration with SharePoint RRS feed

  • Question

  • I have a Sharepoint server 2010 Enterprise in a public domain and a SQL2008 standard in a local domain (with an installation of sharepoint 2010 to support report integration). Does Microsoft support this setup in report server configuration?

    Thursday, April 12, 2012 5:47 PM

Answers

  • I think you asked this over at StackExchange, but you need to install SSRS on your SharePoint Server.  As long as the user account running SSRS has appropriate rights to the SQL Server, then yes, this will work.

    http://sharepoint.nauplius.net

    Thursday, April 12, 2012 6:04 PM
  • In this situation, you don't really have a choice.  SharePoint must be installed on the same server that SSRS is installed on.  I don't believe you can cross a domain boundary with a single farm (e.g. SharePoint Servers need to be members of the same domain).  You could bring in a second SharePoint Server, joint it to the farm as an App Layer, and install SSRS on it.  That way users are visiting your WFE and SSRS is just making web service calls between the two.

    But I wouldn't be too concerned about installing SSRS on an Internet-facing SharePoint Server, personally.  It is yet something else you'll have to keep up with security updates, though.

    Remember that SSRS requires authentication -- it won't work for anonymous users.


    http://sharepoint.nauplius.net

    Thursday, April 12, 2012 7:27 PM

All replies

  • I think you asked this over at StackExchange, but you need to install SSRS on your SharePoint Server.  As long as the user account running SSRS has appropriate rights to the SQL Server, then yes, this will work.

    http://sharepoint.nauplius.net

    Thursday, April 12, 2012 6:04 PM
  • Hey Trevor

    Yes I did. I just thought I'd get different views. Anyways, I have the Reporting Server Add-in on my Sharepoint server(public domain) and the SSRS iteself setup while installing my instance on the SQL2008 Box (Local Domain). And yes, I am using a public domain account to connect to the report server. Is that what you mean? 

    Thanks

    Thursday, April 12, 2012 6:14 PM
  • SSRS (not *just* the rsSharePoint.msi addin!) needs to be installed on your SharePoint Server, not the SQL 2008 box.  The SSRS account needs to be a domain user on the "public domain" with rights on the SQL 2008 box on the "local domain".

    You can't have SSRS SharePoint Integration without installing SSRS on your SharePoint Server.


    http://sharepoint.nauplius.net

    Thursday, April 12, 2012 6:24 PM
  • Trevor

    Isnt that why Microsoft points at installing a sharepoint WFE on the SQl box and attach it to the Sharepoint farm on the public domain?

    Thursday, April 12, 2012 6:29 PM
  • You should never install SharePoint on your Database Engine server.  The setup should be similar to:

    ServerA = SharePoint, SQL Server Reporting Services

    ServerB = SQL Server Database Engine

    But never install SharePoint on a Database Engine server if you can avoid it.


    http://sharepoint.nauplius.net

    Thursday, April 12, 2012 6:32 PM
  • Trevor

    I am pretty new to this and I try to play it safe and just go by Microsfot's tech net articles.

    Here is what I followed: http://msdn.microsoft.com/en-us/library/bb326356.aspx

    Please take a look at point 3.

    Again, please correct me if I am wrong but when you mention "ServerA = SharePoint, SQL Server Reporting Services" does that mean I will be able to install SQL Server Reporting Services without actually having an instance of SQL or are they two different things?

    Thanks

    Thursday, April 12, 2012 6:41 PM
  • I understand where the confusion comes from.  Here is my setup, for instance, using 4 servers:

    1) SharePoint WFE

    2) SharePoint App Layer + SQL Server Reporting Services

    3) SharePoint App Layer

    4) SQL Server Database Engine

    When you configure SSRS on your SharePoint Server, you point it to your SQL Server back end.


    http://sharepoint.nauplius.net

    Thursday, April 12, 2012 6:43 PM
  • Hi GoingForward,

    Microsoft's instructions are often fairly generic, seeming to indicate that you would make your SQL Server a WFE - this works for simpler installations. In a lot of environments, however, such an arrangement is not feasible due the fact that SharePoint often points only to a single instance of SQL on a physical DB server that may host multiple SQL instances.

    A lot of times, the DBA(s) in charge of the SQL backend prefer NOT to have an SSRS instance on the same hardware because they'd prefer the SharePoint admins not have access to the back-end SQL instance. When you configure SQL on a WFE, you can choose to connect to a different SQL server for the database storage, or have the databases hosted directly on the SQL box (in this case, a WFE).

    What you propose (installing a SharePoint WFE on the SQL box with SSRS) and what Trevor proposes (instead installing SSRS on a WFE and hooking SSRS to the DB on a backend server) are not that far apart. Performance and how the farm works are the key considerations here:

    • There will be a performance hit on whichever server hosts SSRS - which of your servers is better suited to take the load?
    • You mentioned that SharePoint is on a public domain and SQL is on a private domain - not quite sure what you mean, but if the SharePoint box is Internet-facing, then perhaps having it host the SSRS instance may not be best (easier target from a security standpoint, more exposed area).

    If the SQL box is under your control, then you must (as Trevor said) install SSRS on a box that is a SharePoint server (WFE role). If you are content with your SQL box doing this task, then you should not allow users to make requests from this box directly - have them use the existing SharePoint server exactly as it is being used now.

    Also, if there is a firewall between the internal facing network and the external facing network, you will need to look up the appropriate TCP ports and open them between these two hosts (again assuming these are on different networks).

    Hope this helps


    Troy Lanphier -- MCT/MCSE/MCITP SharePoint Server 2010 Administration -- Author: Microsoft SharePoint Foundation 2010 Inside Out -- http://blog.sharepointcookbook.com

    Thursday, April 12, 2012 6:50 PM
  • Trevor

    I believe you.

    This is my first time setting it up and I just want to make sure I get it right.  As of now though I am having issues integrating the reporting server (on sql2008 box in local domain) into Sharepoint server (public domain),as you may have noticed from my previous post.

    Would you be able to point me to any links or walkthroughs I can use to set it up to work correctly?

    Thanks again

    Thursday, April 12, 2012 6:52 PM
  • I'm not surprised you're having issues.  Here is what I would do:

    Uninstall SSRS from SQL2008.

    Install SSRS on SharePoint 2010.

    Run the SQL Server Reporting Services configuration utility on SharePoint 2010.

    During the configuration of your ReportServer database, point it to SQL2008 (then move on with the rest of your configuration).

    I don't have any complete guides off hand, but those are the basic steps.


    http://sharepoint.nauplius.net

    Thursday, April 12, 2012 6:57 PM
  • Troy

    Thanks for the explanation. I can really use it. But to quote, the two lines bolded below seem conflicting.

    Please clarify

    "

    • You mentioned that SharePoint is on a public domain and SQL is on a private domain - not quite sure what you mean, but if the SharePoint box is Internet-facing, then perhaps having it host the SSRS instance may not be best (easier target from a security standpoint, more exposed area).

      If the SQL box is under your control, then you must (as Trevor said) install SSRS on a box that is a SharePoint server (WFE role). If you are content with your SQL box doing this task, then you should not allow users to make requests from this box directly - have them use the existing SharePoint server exactly as it is being used now."

    Thursday, April 12, 2012 7:06 PM
  • In this situation, you don't really have a choice.  SharePoint must be installed on the same server that SSRS is installed on.  I don't believe you can cross a domain boundary with a single farm (e.g. SharePoint Servers need to be members of the same domain).  You could bring in a second SharePoint Server, joint it to the farm as an App Layer, and install SSRS on it.  That way users are visiting your WFE and SSRS is just making web service calls between the two.

    But I wouldn't be too concerned about installing SSRS on an Internet-facing SharePoint Server, personally.  It is yet something else you'll have to keep up with security updates, though.

    Remember that SSRS requires authentication -- it won't work for anonymous users.


    http://sharepoint.nauplius.net

    Thursday, April 12, 2012 7:27 PM