We recently migrated from SSRS 2012 to SSRS 2016. We have a few large reports ( 45 - 74 columns that typically returns 30k - 100k records), that took up-to 1 minute to render to Excel on the 2012 SRRS server, but is now taking 6+ minutes to render on the SSRS 2016 server.
Researching different articles online suggested ensuring that Interactive Size is not set to 0, which I confirmed is not the issue. I queried ExecutionLog3 and the results indicate that the most time is spent on rendering the report (i.e. TimeRendering column has the highest value)
The report is calling a stored procedure which is performing a select statements with 4 filters. The report is not performing any complex calculations, groupings, etc on the ssrs server side. The only special formatting in the report is the background coloring for the tablix column headers. I tried rebuilding the report in VS2017 for SSRS 2016 server, but the rebuilt report appears to run longer.
Both the SSRS 2012 and SSRS 2016 servers have 8GB of memory. On the SSRS 2012 server, SQL Server is assigned 4GB of memory. But, on the SSRS 2016 server, SQL Server is assigned 6GB of memory.
The reporting services and db servers are separate. I confirmed that the issue is not related to other large reports running at the same time.
Does anyone have any ideas on changes to the reports or changes to the 2016 SSRS server we should try to get the report to render quicker, similar to the rendering time on the 2012 SSRS server? Please note that reducing the number of columns is not an option according to our business users.