Professional Microsoft® SharePoint® Server 2007 Reporting with SQL Server 2008 Reporting Services
by Coskun Cavusoglu, Jacob Sanford, Reza Alirezaei
11.4. Understanding On-Demand Report Execution
Simply put, when a user clicks a report in a report library, the datasets defined in that report execute and return data to the report server from the underlying data source. Next, the report execution engine uses the report definition file stored in the SharePoint content database to determine how to create the report from the retrieved data, transform it into HTML, and finally push it down through the HTTP pipeline to the user's browser.
Truth to be told, there is more to the report execution process than stated above. The report execution process can be broken into smaller discrete operations. It is important to understand how much processing is required to produce a report, because this helps you make better decisions regarding how reports should be delivered to the end users. For example, if the users don't need to view the most updated version of a specific report, why do they have to go through the report execution process each time they request to view that report? Why not leverage one of the available execution options to generate the report in advance of the user viewing it?
From here on, the goal of this chapter is to introduce techniques to optimize report server capabilities and improve the performance of your reports, which altogether results in a better user experience.
11.4.1. What Goes Where?
The first step in your dive into the report execution process is to understand the set of databases used when you configure ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access