separating SSRS from Database server - SQL server 2016 standard

  • when SSRS component is installed on a different server from Database server, will there be any performance gains?  Database and SSRS run on separate physical servers.

    Is it also possible to run SSRS on SQL Server 2008 R2 and  the database on SQL Server 2016 standard.

    Thanks  in Advance !!

  • bgz30 - Tuesday, July 11, 2017 2:08 PM

    when SSRS component is installed on a different server from Database server, will there be any performance gains?  Database and SSRS run on separate physical servers.

    Is it also possible to run SSRS on SQL Server 2008 R2 and  the database on SQL Server 2016 standard...

    Regarding your 1st question: to quote Yogi Berra, " In theory - practice and theory are the same thing, in practice they are not."

    In theory, yes. Absolutely BUT there are a lot of variables to consider, too many to list here. SQL Server is a very resource intensive and so is SSRS; splitting them up makes CPU, memory and I/O bottlenecks less likely and adds a layer of fault tolerance (e.g. some badly written custom .net code crashing your SSRS box does not kill you mission critical SQL instance.)

    Unless its a small environment with a light workload and limited budget, I prefer to have SSRS, SSIS and/or SSAS  running on their own servers without any SQL Server service(s) running. I prefer to have my ReportServer and other MS BI stack catalog databases (such as SSISDB) running on a SQL instance. 

    Regarding SSRS 08 & SQL Server 2016: as far as I know there shouldn't be a problem but check the minimum requirements for SSRS.

    "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 2 posts - 1 through 2 (of 2 total)

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