Share via


Available Rendering Extensions (Report Builder 2.0)

Export formats are supported through rendering extensions that are installed on the report server. There are three types of renderers:

  • Data renderers   Data renderers strip all formatting and layout information from the report and display only the data. The resulting file can be used to import the raw report data into another file type, such as Excel, another database, an XML data message, or a custom application.

    The following data renderers are supported: CSV and XML.

  • Soft page-break renderers   Soft page-break renderers maintain the report layout and formatting. The resulting file is optimized for screen-based viewing and delivery, such as on a Web page or in the ReportViewer controls.

    The following soft page-break renderers are supported: Microsoft Excel, Microsoft Word, Web archive (MHTML), and the ReportViewer controls.

  • Hard page-break renderers   Hard page-break renderers maintain the report layout and formatting. The resulting file is optimized for a consistent printing experience, or to view the report online in a book format.

    The following hard page-break renderers are supported: TIFF and PDF.

Note

When you design your report in a Reporting Services authoring tool and preview the resulting report, the report is first rendered in HTML in the Report Viewer.

The following table describes the rendering formats you can use to export your report. For more information about which rendering extension to use, see Understanding Rendering Behaviors (Report Builder 2.0) and Comparing Interactive Functionality for Different Report Rendering Extensions (Report Builder 2.0).

Renderer Type

Format

Description

Recommendations

Soft page-break renderer

Excel

Opens a report in Microsoft Excel.

Use this format to work with report data in Excel 2000 or later versions.

For more information, see Exporting to Microsoft Excel (Report Builder 2.0).

Soft page-break renderer

Word

Opens a report in Microsoft Word.

Use this format to work with report data in Word 2000 or later versions.

For more information, see Exporting to Microsoft Word (Report Builder 2.0).

Soft page-break renderer

Web archive

Opens a report in MHTML. The report opens in Internet Explorer.

In contrast with other HTML rendering extensions, the Web archive format produces a self-contained, portable report (embeds images within the report). Use this format to view HTML reports offline or for e-mail-based delivery.

For more information, see Rendering to HTML (Report Builder 2.0).

Hard page-break renderer

Acrobat (PDF) file

Opens a report in Adobe Acrobat Reader (version 6.0 or later).

Use this format to create PDF versions of a report that can be opened in PDF viewers that support PDF 1.3 or later.

For more information, see Exporting to a PDF File (Report Builder 2.0).

Hard page-break renderer

TIFF

Opens a report in a page-oriented format.

Use this format to create image versions of a report.

For more information, see Exporting to an Image File (Report Builder 2.0).

Data renderer

XML

Opens a report in XML.

Use this format to copy report data from a report server to other applications or servers.

For more information, see Exporting to XML (Report Builder 2.0).

Data renderer

CSV

Opens a report in comma-delimited format. The report opens in an application associated with CSV file formats.

Use this format to copy report data from a report server to other applications or servers.

For more information, see Exporting to a CSV File (Report Builder 2.0).

Configuration Options

These rendering extension options are made available through configuration settings. Export functionality can vary from one report server installation to the next based on these settings.

  • A developer can set URL parameters that hide a report toolbar from a report, preventing the use of the export option and other toolbar features.

  • A developer can set URL parameters that render the report in a specific output format.

  • A report server administrator can add or remove rendering extensions from configuration files, determining which export formats are available from the drop-down list.

  • A report server administrator can specify device information settings that override default rendering behavior.

The export formats that are available on a report server are defined through rendering extension settings in the Reporting Services configuration files. To make a rendering extension unavailable, users with the appropriate permissions can remove the rendering extension setting from the Render setting of the RSReportServer.config file located on the report server.

You cannot vary extension availability for specific groups, users, or reports. For more information, see : "RSReportServer Configuration File," "Customizing Rendering Extension Parameters in RSReportServer.Config," "Using a URL to Access Report Server Items," "Using URL Access Parameters," "Managing Report Server Content," "Subscription and Delivery," and "Creating, Modifying, and Deleting Snapshots in Report History" in the Reporting Services documentation in SQL Server Books Online.