Reports, Report Parts, and Report Definitions (Report Builder 3.0 and SSRS)
Reporting Services uses a variety of terms to describe a report in different states, including the initial definition, the published report, and the viewed report as it appears to the user.
You can create and modify report definitions (.rdl) in Report Builder 3.0 and in Report Designer in Business Intelligence Development Studio. Each authoring environment provides different ways to create, open, and save reports and related items. For more information, see Designing Reports in Report Designer and Report Builder 3.0 (SSRS) on the Web at microsoft.com.
A report definition is a file that you create in Report Builder or Report Designer. It provides a complete description of data source connections, queries used to retrieve data, expressions, parameters, images, text boxes, tables, and any other design-time elements that you might include in a report. Although report definitions can be complex, at a minimum they specify a query and other report content, report properties, and a report layout.
Report definitions are rendered at run time as a processed report. At that time, the data is retrieved from the data source and formatted according to the instructions in the report definition. A report definition can be run directly from your computer and saved locally, or it can be published to a report server for others to run as well.
Report definitions are written in XML that conforms to an XML grammar called Report Definition Language (RDL). RDL describes the XML elements, encompassing all possible variations that a report can assume. For more information about report definitions or RDL, see Designing Reports in Report Designer and Report Builder 3.0 (SSRS) and Report Definition Language Reference.
The Visual Studio Report Designer produces client report definition (.rdlc) files for use with the ReportViewer control. The .rdlc files can be converted to .rdl files for use with Reporting Services Report Designer. For more information about .rdlc files, see the Visual Studio documentation and Reporting Services and ReportViewer Controls in Visual Studio 2010.
A report part definition is an XML fragment of a report definition file. You create report parts by creating a report definition, and then selecting report items in the report to publish separately as report parts. Report parts include data regions, rectangles and their contained items, and images. You can save a report part with its dependent datasets and shared data source references so it can be reused in other reports.
Report parts are self-contained report items that are stored on the report server and can be included in other reports. Use Report Builder to browse and select parts from the Report Part Gallery to add to your reports. Use Report Designer or Report Builder to save report parts for use in the Report Part Gallery. For more information, see Report Parts (Report Builder 3.0 and SSRS) and Report Parts in Report Designer (SSRS) on the Web at microsoft.com.
After you create an .rdl file, you can save it locally, or save it to a personal folder (such as the My Reports folder) on the report server. When the report is ready for others to see, you publish it by saving it from Report Builder to a public folder on the report server, uploading it through Report Manager, or deploying a report project solution from Report Designer. A published report is an item that is stored in a report server database and managed on a report server or SharePoint site.
A published report is secured through role assignments using the Reporting Services role-based security model. Published reports are accessed through URLs, SharePoint Web parts, or Report Manager, or you can navigate to and open them in Report Builder.
A report can also be published as a snapshot that contains both layout information and data as of the time the report was initially run. Report snapshots are not saved in a particular rendering format. Instead, report snapshots are rendered in a final viewing format (such as HTML) only when a user or an application requests it. For more information, see Finding and Viewing Reports in Report Manager (Report Builder 3.0 and SSRS).
A rendered report is a fully processed report that contains both data and layout information in a format suitable for viewing (such as HTML). Until a report is rendered into an output format, it cannot be viewed. You can render a report by doing one of the following:
Create or open a report in Report Builder or Report Designer and run it.
Find and run a report in Report Manager.
Find and run a report on a SharePoint site that is integrated with a Reporting Services report server.
Subscribe to a report, which is delivered to an e-mail inbox or a file share in an output format that you specify.
Subscribe to a report, which is delivered to an e-mail inbox or a file share in an output format that you specify.The default rendering format for a report is HTML 4.0. In addition to HTML, reports can be rendered in a variety of output formats, including Excel, Word, XML, PDF, TIFF, and CSV. As with published reports, rendered reports cannot be edited or saved back to a report server. For more information, see Exporting Reports (Report Builder 3.0 and SSRS).