We have an issue where the ASP .net Reporting Application we are using is running at a significantly slower pace than the Report Manager portal, when it comes to running large reports. One of the possible solutions being considered is switching from RDL (server-based reports) to RDLC format (client-side-based). Is this a feasible solution for such an issue? Initial research suggests that performance can be significantly improved using RDLC. However, we have over 100 reports that currently reside on our Report Server. Do we need to do any major configuration or individual tweaking on each of these to convert them to RDLC? Furthermore, I have read that the Report Viewer control does not support local parameter prompting. This is because the Report Viewer does not execute queries itself, but merely displays the results executed by the host application. How would this affect the current server-side reports, some of which use up to a dozen parameters each to populate stored procedures used for their report datasets? Would switching from RDL to RDLC be worth it considering these issues? Any insights or suggestions would be really appreciated!
↧
