Post reply

Centralized SSRS instance using multiple data sources

  • February 20, 2015 at 9:50 am

    #294796

    What are the pros and cons related to having one central reporting services instance used by different developer groups that uses multiple data sources to access different database servers? For instance, I know a pro would be that we would only be paying for one license. A con would be that there is a single point of failure for every report. Do many shops use this design? We have several SSRS installs but each one is on it's own app server that creates the SSRS databases on the database server that houses the user databases that the reports will be using. By doing this we are paying for multiple licenses. Could we just have one centralized SSRS install and utilize all of these same reports by creating data sources for each that would point to the appropriate database server?

  • February 20, 2015 at 10:17 am

    #1779001

    Wildcat91 (2/20/2015)

    Could we just have one centralized SSRS install and utilize all of these same reports by creating data sources for each that would point to the appropriate database server?

    Yep, and just set up access to report folders as appropriate.

    Only thing for me would be to check the server it's running on is suitably powerful.

    You could also look into scale-out deployment if you're using Enterprise/BI Editions.

  • February 20, 2015 at 11:59 am

    #1779036

    Ditto what Gazareth said...

    Do many shops use this design?

    My experience has been - yes.

    "I cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code."

    -- Itzik Ben-Gan 2001

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply