Hiding parameter area when viewing reports

When rendering reports, oftentimes the application would like to minimize as much of the non-report area of the viewer control as possible.  This is easily accomplished when rendering the report through the built-in report viewer control hosted in the ReportServer web site (http://servername/reportserver).  There are two parameters which control the rendering of the viewer control…

1

Hiding Rendering Extensions

This is documented behavior, but we see lots of questions on it.  A good mechanism for preventing users from accidently exporting reports to a format that you don’t want (for example, you might know that the report doesn’t render quite right in a particular format) is to mark the extension as “invisible” in the Report…

1

Scaling out the Viewer Control and rsExecutionNotFound

One of the criteria that the report server uses to match the provided SessionID with a stored report is that the SessionID has to be provided by the same user that initially created the session.  Usually, this is the case.  Someone browses the report in IE, they click around to paginate or expand toggles, and…

0

Scaling Up: SSRS 2008 vs. SSRS 2005 (spoiler: 2008 wins)

The SQL Customer Advisory Team just released a Technical Note comparing SQL Server Reporting Services 2008 vs. 2005 from a scale-up perspective.  Its good to see that a lot of the work that we did over this release focusing on performance and scalability (across the board, from the core server/processing infrastructure to specific rendering extensions) has…

0

All those temporary files (RSTempFiles)

When you install Reporting Services, we create a few directories: LogFiles ReportManager ReportServer RSTempFiles Most of these are fairly self explanatory.  LogFiles… well we put our log files in there.  ReportManager contains the Report Manager application (what you get when you browse to http://<server>/reports) and ReportServer contains the Report Server application which is the proper…

0

Where has John been?

Ok, it has been a little while.  But I have been pretty busy lately.  His name is Christopher. We have also been pretty busy locking down Katmai to get CTP6 (aka known as the “February CTP”) out the door and working bugs.  I recommend that people head over towards the “Katmai” forum on MSDN for…

0

Memory Management in Reporting Services 2008

One of the big pushes for SSRS 2008 has been to reduce the occurrence of OutOfMemoryExceptions caused during report execution.  A lot of work has gone into making this happen throughout the report rendering stack, including significant changes in the report processing engine to move a definition based object model as opposed to an instance…

2

SQL Server 2008 (Katmai) and Reporting Services

Today the first public release of SQL Server 2008 is shipping.  Of course, Reporting Services is still there in the box.  You can find general information about the release here: https://connect.microsoft.com/SQLServer/content/content.aspx?ContentID=5395&wa=wsignin1.0 There are also some Katmai specific MSDN forums, and a Katmai Reporting Services MSDN forum. 

0

Diagnosing Reporting Services Issues

I was poking around some other SSRS blogs from folks here on the product team, and I found this post from Lukasz about troubleshooting Reporting Services.  It is a great overview of some of the guidance we have given in the form of whitepapers, KB artciles, and a bunch of other sources.  I highly recommend…

0

ReportServerTempDB IO Saturation

Reporting Services uses a temporary database for storage of objects which are, well, temporary.  For example, report snapshots which are associated with a particular user session as the result of a live execution.  Cached report snapshots are also stored here because they begin life as a result of a live report execution.  This means that…

1