|
All, We have an issue moving from SSRS 2008 to SSRS 2008 R2. A report on SSRS 2008 server runs in 5 or 10 seconds. When I deploy it to our 2008 R2 server, it takes around 5 MINUTES to run! I reckon this is a bug in SSRS 2008 R2, and would like some feedback from other users. Could some of you please deploy the attached report to your 2008 and/or 2008 R2 servers and let me know how long it takes to view the report from a browser? I have attached the report as TestPerf.txt (you'll need to change the extension to RDL). Thanks in advance.
(comments are locked)
|
|
@xnl28 - from your description it really does sound like a bug - I would not continue searching for other affected people, but rather file a bug with Microsoft. Either open a support call (may cost you money), or file a connect item over at http://connect.microsoft.com/. @William: I have already opened bug report on Connect https://connect.microsoft.com/SQLServer/feedback/details/737342/internet-explorer-rendering-of-ssrs-report-with-large-number-of-rows-is-extremely-slow-in-2008-r2-compared-to-2008
Apr 19 '12 at 01:15 PM
xnl28
excellent! I have voted on that too. Maybe MS will fix it - have you tried out SQL 2012 to see if it has been fixed through that release?
Apr 19 '12 at 01:44 PM
WilliamD
Great, thanks. I've not tried it in SQL 2012, that's a good idea.
Apr 20 '12 at 07:42 AM
xnl28
I have just tried the report in SSRS 2012 (version 11.0.2100.60) and the issue remains. It takes 86 seconds for the report to complete compared to 7 seconds in SSRS 2008.
Apr 27 '12 at 07:59 AM
xnl28
(comments are locked)
|
|
Does this report consistently run slower on your 2008R2 server or just the first time you run it? Have you tried running IE as administrator? Right click, chose run as administrator. Are you running the report through IE on a client or on the server?
Apr 17 '12 at 07:03 PM
Tim
@Tim: I don't think running IE as administrator would make a difference, because when use IE to run the report deployed to the SSRS 2008 server, it completes in 5 - 10 seconds. Have you tried running the report I attached in the original post? I am more interested in what performance other people get when running the report in 2008 and 2008 R2.
Apr 17 '12 at 07:27 PM
xnl28
(comments are locked)
|
|
So it seems to relate to the same issue like in your previous post. The KB FIX: Performance decreases after you move a large report to SQL Server 2008 R2 Reporting Services. Maybe a trying a workaround mentioned in the BK
Don't have R2 instance and time currently available to play with it. But if will have a little more time I will try to test it on R2 instance. @Pavel: Yes, it's the same issue. In this question, I am asking other users to post the performance times they get with the test report I attached. The R2 server I'm using is on cumulative update #5 for SSRS 2008 R2 service pack 1, which is version 10.50.2806.0. This should include the fix you refer to, but the performance is still a serious problem, so there is another issue that requires fixing. Thanks for your suggestions. If you do get time to test the RDL I attached, that would be very helpful.
Apr 17 '12 at 09:46 PM
xnl28
(comments are locked)
|
|
I think we're seeing the same issue over here. The reports run fine on 2008, but take excessive time in R2 and 2012. This effects the same IE 8 and 9, but Chrome runs very very fast.
(comments are locked)
|
|
Microsoft have confirmed the issue I've described is a bug, and it will be fixed in the first service pack of SQL 2012. Hotfixes for previous versions of SQL can be obtained from Microsoft. Please see Connect ID 737342. Thanks to all for your suggestions and advice. Did you tested this with SP1 for SQL 2012? As SP1 was released about 2 weeks after the original release of SQL Server. :-)
Jun 19 '12 at 07:34 PM
Pavel Pawlowski
I didn't know SP1 for SQL 2012 was out - I can't find any article about it on MSDN...
Jun 21 '12 at 10:50 AM
xnl28
There are 2 Cumulative Updates , but no Service Pack yet: http://support.microsoft.com/kb/2692828
Jun 21 '12 at 12:01 PM
Kev Riley ♦♦
Ah, you are right @Kev. It's cummulative update. But anyway the @@VERSION tells SP1 :-) Microsoft SQL Server 2012 - 11.0.2316.0 (X64) Apr 6 2012 03:20:55 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) (Hypervisor)
Jun 21 '12 at 12:23 PM
Pavel Pawlowski
@Pavel the SP bit refers to the windows server build - I too have been confused by this message before!!!
Jun 21 '12 at 12:29 PM
Kev Riley ♦♦
(comments are locked)
|
1 2 next page »
Have you take a look on the executions statistics stored in the
[ExecutionLogStorage]table in the Report Server database?If not, take a look on the TimeDataRetrieval, TimeProcessing and TimeRendering to find out what causes the long execution.
@Pavel: Yes, I checked all those figures before posting the question. The total of TimeDataRetrieval, TimeProcessing and TimeRendering averages about 2 or 3 seconds over several runs. So the huge time in 2008 R2 is due to Internet explorer rendering the report (not the server rendering the report)
@xnl28 Did you seek help from Microsoft? (You said you will in earlier thread) If yes, then what is the response you got?
@xnl28 First thing noticed in your report is that Tablix's "KeepTogether" property is set to TRUE, which means that you want all your data on one page? This itself could decrease the performance. Try setting that property to FALSE and please let us know the result.
It is simple because there is a bug in 2008 R2. If you cannot live with the workarounds then wait for a CU/Service Pack OR whatever the Microsoft suggests.
Having said that, I would request not to post new questions with the same. You can always update your pending threads to seek help. This way everyone would have the background readily available and can give you better support. Thanks.