September 13, 2011 at 2:27 pm
Hi,
The stored procedure that generates data works very well. It retrieves 20K+ rows just in a second. When viewing a SSRS2008 report in preview mode on Visual Studio, it also works fine. But after deploying a report to a reporting server and running a report through a browser, the report froze for a while but I got the result finally. It happens just a few reports. With the same amout of data, a report runs quick in SSRS 2005.
Does anyone has an idea to solve this problem? Pls recommend me.
Thank you,
Pam
September 13, 2011 at 2:47 pm
See if this is of any help.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 14, 2011 at 8:30 am
It can be the case (I have this experience) that this is actually not SP or report issue but rather how browser renders this 20K+ records. Try using input parameters that results in smaller output (let say 1K rows only)-
this can help in finding issue reason
September 14, 2011 at 4:55 pm
Hi,
I limits the query to retrieve data only 1000 rows. The report is still be the same. It freeze about 15-20 minutes but returns the result finally.
There is a warning sign on the bottom left corner and the error message is:
--------------------
ERROR MESSAGE:
--------------------
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; .NET4.0C; .NET4.0E)
Timestamp: Wed, 14 Sep 2011 22:47:52 UTC
Message: Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 12030
Line: 5
Char: 62099
Code: 0
Message: Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 12030
Line: 5
Char: 62099
Code: 0
Please share experience if you have a solution. Thank you.
September 14, 2011 at 5:01 pm
your connection is getting aborted/terminated.
When running this report - are you running it from multiple locations to see if it behaves the same everywhere (e.g. from the report server and from some desktop machines)?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 15, 2011 at 10:39 am
Hi Jason,
I ran the report on another machine using IE8; the result is the same. The report froze for a long time but got a result finally.
I tried this report on Firefox 6.0.2. The report was working fine and return the resulted within a reasonable time period.
Would the problem solve if I upgrade IE to newer version? The organization I works for uses IE as a standard browser.
September 15, 2011 at 10:42 am
You can try the upgrade of the browser - looks like it may be a memory leak in IE if FF is returning reasonably quickly.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 19, 2011 at 9:10 pm
I'm back again. From my previous post, I still won't be able to solve the problem as upgrading IE8 to newer version seems not to be a solution. I tried to remove all report parameters and ran the report; it works very well. Then I added report parameters back with hardcode value to filter the result, the report was a bit slower but still good. When I added queries to report parameters to populate data and viewed report, the report then froze. One of query in report parameters returns 20K+ rows of data.
Could this the cause of IE freeze?
Should I check or change any configuration on reporting server to fix this problem?
Thanks.
September 19, 2011 at 9:44 pm
A couple of things to try. First set WorkingSetMaximum in the RSReportServer.config file. Configure SQL server Max memory.
Here's a link on the WorkingSetMaximum.
This has been of some help to me.
Also, check the queries that provide the datasets - and adjust for Parameter Sniffing.
I have seen people recommend using option recompile for this issue (I have been running into it lately as well) - I am not ready to recommend that nor to implement that at this point.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply