SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Does anyone have experience with the following issue? Are there any known workarounds?

Official MS Statement: General overhead performance differences when you view reports in SharePoint integrated mode versus in SharePoint native mode:

Further info:

Furthermore, the performance of individual reports viewed using the ASP.NET Ajax-enabled Report Viewer web part in SharePoint 2010 degrades significantly when there are multiple viewers on a single web page, the viewer generates very large HTML, and the web page is viewed using older browsers.

“This performance problem seems to be particularly noticeable on pages with a larger number of valid values in a parameter, a large report page, or multiple viewers (or web parts) on a single page“

share|improve this question

closed as off topic by Alex Angas May 18 '11 at 0:27

Questions on SharePoint Stack Exchange are expected to relate to SharePoint within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

This question has been closed due to the site policy described here. Please add any comments you have about the closure to that topic. – Alex Angas May 18 '11 at 0:28

One workaround is to look at the structure of your pages. Consider what information your user requires on each page. If some information is almost never used place it on a separate page.

That way you will be able to give the users most information they need reasonably quickly, while requiring an extra request for information that is not used as often.

share|improve this answer

I've found that an SSRS report will repeatedly make calls back to the report server, even if it's a report that contains no data. This can cause problems if you have a report on the front page of your portal, as users may tend to keep that page open, causing massive hits on your report server. Brought down our portal in the first couple of hours on a Monday morning with ~4000 users. Took the report off the front page and everything went back to normal.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.