Hi all, I'm experincing a big performance problem with Reporting Services reports. I'm publishing the reports on a new server with installed: - Windows Server 2008 R2 x64 - CPU 2 Xeon quad core 3.00Ghz - RAM 16Gb - Disks SAN - SQL Server 2008 R2 x64 Standard Edition (10.50.1600.1) After the deploy of the reports (connecting to an SSAS cube) I'm expecting to have a fast access to reports, but they are very very slow, and I can't understand why. During the report rendering seems that the server is in idle time! The reports deployed on a 32bit server (with WS 2003 R2 + 2 Xeon double core + 4Gb of RAM) are more and more faster! Do you have an idea on why? Many thanks to everyone, specially to who will solve my issue! Best regards Davide Brevi

Can you connect to the new report server and see which one takes time, data retrieval or rendering. use ReportServer select * from ExecutionLog2 Also collect the same info from old server and see where is the blockage. Regards Suresh http://skamie.wordpress.com

Follow an extraction of the ExecutionLog2 view: Server TimeDataRetrival TimeProcessing TimeRendering Source Status ByteCount RowCount Old x32 2418 605 62 Live rsSuccess 24828 177 New x64 8908 10054 43 Live rsSuccess 22003 145 Seems the problem is related on TimeDataRetrival and TimeProcessing. Best regardsDavide Brevi

While the data retrival corresponds to the exection of the data set, the processing time involves Grouping, sub report processing etc. In the new server this seems to be more. Any idea whether the load on the new server is same as the old one or any differences? Also can you let me know whether the old report was also pointing to same cube? If yes, then we need to identify why the data retival from the same source is different. You can use the profiler to trace the Analysis Service and see what is the difference between queries fired between the old and the new reprot server. Can you also check the additionalinfo column in the ExecutionLog2 and see whether Scalability sum is high, which indicates there is some memory pressure. Regards Suresh http://skamie.wordpress.com

Additional info are: <AdditionalInfo> <ProcessingEngine>2</ProcessingEngine> <ScalabilityTime> <Pagination>0</Pagination> <Processing>0</Processing> </ScalabilityTime> <EstimatedMemoryUsageKB> <Pagination>4</Pagination> <Processing>77</Processing> </EstimatedMemoryUsageKB> <DataExtension> <SQL>1</SQL> <OLEDB-MD>17</OLEDB-MD> </DataExtension> </AdditionalInfo> I'm supsecting that something is different between x32 and x64 server for the cube access! Davide Brevi

Hi Davide, Based on the log info of executionlog2, this issue is caused because much time are taken in data retrieval,report processing boostrap and tablix processing. Could provide more details about the SSAS version and how to build this report using the cube? See http://blogs.msdn.com/b/robertbruckner/archive/2009/01/05/executionlog2-view.aspx about Analyzing and Optimizing Reports. thanks, Jerry

Thanks for your answer. my IT raised an issue on hardware installation, and disks performances. They are reinstalling all the hardware, probably with Windows Server 2003 x64. I'll keep you informed dDavide Brevi

All, I've fond the solution to my problem. It's related on the access of cube, as supposed. To access the cube I've tried different ways: using (local)\[instancename] or [IP]\[instancename] or [servername]\[instancename] Only today I've found that Windows Server 2008 doesn't set by default the hosts file with the localhost value: 127.0.0.1 localhost but windows server 2003 did this! Including this configuration in the hosts file the problem is solved!!! Thanks for suggestions Best Regards dDavide Brevi

Hi Davide, I am facing performance Issues with SSRS 2008 r2. My data source is a cube, Can you please provide me with steps (on how you resolved your Problem " 127.0.0.1 localhost " Thanks, Devi

Thanks Davide, I tried your solution.