Hi, I am rather disappointed with Report Builder (3.0 - SQL Server 2008 R2). After reading up about it, and seeing what it can do, I went full-steam ahead with an implementation. The SSRS reports (running off either views or SSAS cubes) work quite well, and look rather presentable. I was then asked to give users some flexibility with regards to creating their own reports, which eventually lead me to Report Builder. I installed the latest version (also tried the ClickOnce option via IE), but the performance is absolutely atrocious to say the least. I have tested various options, involving running it off really basic views. Now, to be honest, the data sets I'm working with is rather large, but surely SQL Server, and Report Builder, should be able to handle large data sets - I tried to test it with even more basic views to filter the data sets to present less information, but the performance didn't increase much... Am i missing something vital, or is there perhaps some settings I could look at to improve performance? I was testing this on the actual SQL Server server, so that would eliminated any network-related issues. It's running on a Windows Server 2008 64bit server with 64Gb of RAM. Please help - I am really very disappointed so far! Thank you for any advice / help...

If your reports are performing slow, then you may need to optimize your SSRS. If you are working with large datasets, optimization is important. It is also very important the order of the parameters. If you are running Reporting Services in Integrated Mode with SharePoint, then it will perform very slow, unfortunately.

Hi, I am working with huge data sets, yes. How would I be optimising SSRS - any specific things I could check? Also, I'm not putting the reports on SharePoint as yet, as I am aware of potential performance issues. Thank you for the reply though. Regards, W

To optimize your reports you could: Use parameters for your dataset instead of filtersSelect fewer columns, only those you needUse drill-downs and groupingUse subreports (with caution)

How long do the queries for the reports take to execute? When you say large... how many rows and how many columns? And what is your report typically doing, is it a data type or performing calculations? Can you go to the ExecutionLog3 view and post some typical performance times.. CheersJosh Ash

Hi For an overview on performance tuning try SQL Server performance tuning overview Run a view outside of SSRS and see how long it takes. In SSRS there is execution log that tells you how long it takes to retrieve data but also render it on the report before it is presented to end users. If no one is managing indexes on your tables than this is most likely you problem. Hope that helps Emil

Hi PsyberFox, Thanks for your posting. The report performance issue is usually a complex issue. In Reporting Services, there are three processing phases when we view a report: data retrieve, report process and report rendering. To find out how many milliseconds of processing time is spent on each processing phase when we view a report on the report manager or a SharePoint site, we can view the report server execution log via the SSMS. For more information about analyzing and optimizing reports, please see Roberts blog below: ExecutionLog2 View - Analyzing and Optimizing Reports Irusul and Emil have posted good suggestions about optimizing report on SSRS level and database table level. For more information about troubleshooting report performance and optimizing report processing, you can refer to: Troubleshooting Reports: Report Performance Besides, to improve the performance on the report server, you can enable the report cache. As a performance-enhancement technique, caching can shorten the time required to retrieve a report if the report is large or accessed frequently. For more information, please see: Caching Reports Hope this helps. Regards, Mike Yin