SQL Server Reportin => Understanding Report Layout and Rendering
- View Source
Understanding Report Layout and Rendering
A report consists of three main areas: a page header, a page footer, and the body. The page header and footer repeat the same content at the top and bottom of each page of the report. You can place report items such as images, text boxes, and lines in headers and footers. The body of the report contains the report data. In addition to the report items that you can place in a header or footer, you can place data regions, which display the data from a dataset, anywhere in the report body.
The placement of report items in a report is completely freeform. With Reporting Services, you are not limited to "bands" of data in a report. You can place data regions with different sets of data side-by-side. Certain report items can also contain other report items. For data regions, this means that you can nest groups of data within other groups.
When you run a report, the report server combines the layout from the report definition with the data from the data source, and renders the report in a specified format. The report server uses extensions to perform much of this work: a data processing extension is used to retrieve the data based on the type of data source, and a rendering extension is used to provide report output based on the selected format. Different extensions can change the way data is processed and the report is rendered.
Pagination in a report is determined by the page size of the report and any page breaks placed on report items. Rendering extensions that support page size, such as image and PDF, format the data in the report to fit within each page. Rendering extensions that do not support page size, such as HTML, render all data between page breaks on a single page. All rendering extensions that support page breaks on items will start a new page after each page break in the report.
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!