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.: http://ask.sqlservercentral.com/storage/temp/174-TestPerf.txt
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.
answered Jun 19 '12 at 04:45 PM
Does this report consistently run slower on your 2008R2 server or just the first time you run it?
answered Apr 17 '12 at 04:38 PM
What makes you think it is a bug? What does the execution plan for each instance show you?
When I reviewed the plan I got from the query it shows the "Optimization Level" as "TRIVIAL". What I have [read] this simply means the query is not going through the full optimization process by the optimizer due to certain requirements. I don't have a SQL 2008 instance but ran the query on SQL 2008 R2 (SP1) and SQL 2005 (SP4) and got the same plan and same time to run it. I don't have a report server to deploy it to.: http://sqlinthewild.co.za/index.php/2009/12/08/are-trivial-plans-cached/
answered Apr 17 '12 at 06:28 PM
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.: http://support.microsoft.com/kb/2506799/en-us
answered Apr 17 '12 at 09:18 PM
@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/].: http://connect.microsoft.com/
answered Apr 19 '12 at 09:27 AM