Exporting Reports (Report Builder and SSRS)
After you run a report, you can export it to another format, such as Excel or PDF, or export the report by generating an Atom service document, listing the Atom-compliant data feeds available from the report.
Export a report to do the following:
Work with the report data in another application. For example, you can export your report to Excel and then continue to work with the data in Excel.
Print the report in a different format. For example, you can export the report to the PDF file format and then print it.
Save a copy of the report as another file type. For example, you can export a report to Word and save it, creating a copy of the report.
Use report data as data feeds in applications. For example, you can generate Atom-compliant data feeds that the SQL Server 2016 Power Pivot client can consume, and then work with the data in Power Pivot.
The export option is available on the report viewer toolbar in Report Manager, which appears at the top of every report when you view a report on the report server, and on the ribbon in Report Builder when you preview a report. The data feed option is available only in Report Manager.
Reporting Services provides many rendering extensions, supporting exports of reports to common file formats. The rendering extensions support file formats with soft breaks (for example, Word or Excel), hard-page breaks (for example, PDF or TIFF), or data only (for example, CSV or Atom compliant XML).
To quickly get started with exporting reports and generating Atom-compliant data feeds from reports, see Export a Report as Another File Type (Report Builder and SSRS) and Generate Data Feeds from a Report (Report Builder and SSRS).
You can create and modify report definitions (.rdl) in Report Builder and in Report Designer in SQL Server Data Tools. 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 (SSRS) on the Web at microsoft.com.
There are three types of Reporting Services rendering extensions:
Data renderer extensions Data rendering extensions 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. Data renderers do not support page breaks.
The following data rendering extensions are supported: CSV, XML, and Atom.
Soft page-break renderer extensions Soft page-break rendering extensions 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 rendering extensions are supported: Microsoft Excel, Microsoft Word, and Web archive (MHTML).
Hard page-break rendering extensions Hard page-break renderer extensions 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 rendering extensions are supported: TIFF and PDF.
Reporting Services provides rendering extensions that render reports in different formats. If you plan to use this feature, you should optimize the report design for your chosen file format. The topic about each rendering extension provides detailed information about how the report is rendered to that format.
The following table lists the available formats.
Rendering Extension Type
The Comma-Separated Value (CSV) rendering extension renders reports as a flattened representation of data from a report in a standardized, plain-text format that is easily readable and exchangeable with many applications.
For more information, see Exporting to a CSV File (Report Builder and SSRS).
The Excel rendering extension renders a report as an Excel document that is compatible with Microsoft Excel 2007-2010 as well as Microsoft Excel 2003 with the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint installed. The report is exported to an Excel worksheet with some layout and original design elements stripped out. Properties of the report and groups within the report can be set to enable the naming of worksheet tabs upon export to Excel. The file name extension of files generated by this renderer is xlsx.
For more information, see Exporting to Microsoft Excel (Report Builder and SSRS).
The Word rendering extension renders a report as a Word document that is compatible with Microsoft Word 2007-2010 as well as Microsoft Word 2003 with the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint installed. After the report is exported to a Word document, you can change the contents of your report and design document-style reports such as mailing labels, purchase orders, or form letters. The file name extension of files generated by this renderer is docx.
For more information, see Exporting to Microsoft Word (Report Builder and SSRS).
The HTML rendering extension renders a report in HTML format. The rendering extension can also produce fully formed HTML pages or fragments of HTML to embed in other HTML pages. All HTML is generated with UTF-8 encoding.
The HTML rendering extension is the default rendering extension for reports that are previewed in Report Builder and viewed in a browser, including when run in Report Manager.
For more information, see Rendering to HTML (Report Builder and SSRS).
Acrobat (PDF) file
The PDF rendering extension renders a report to files that can be opened in Adobe Acrobat and other third-party PDF viewers that support PDF 1.3. Although PDF 1.3 is compatible with Adobe Acrobat 4.0 and later, Reporting Services supports Adobe Acrobat 6 or later. The rendering extension does not require Adobe software to render the report. However, PDF viewers such as Adobe Acrobat are required for viewing or printing a report in PDF format.
For more information, see Exporting to a PDF File (Report Builder and SSRS).
The Image rendering extension renders a report to a bitmap or metafile. By default, the Image rendering extension produces a TIFF file of the report, which can be viewed in multiple pages. When the client receives the image, it can be displayed in an image viewer and printed.
The Image rendering extension can generate files in any of the formats supported by GDI+: BMP, EMF, EMFPlus, GIF, JPEG, PNG, and TIFF.
For more information, see Exporting to an Image File (Report Builder and SSRS).
The XML rendering extension returns a report in XML format. The schema for the report XML is specific to the report, and contains data only. Layout information is not rendered and pagination is not maintained by the XML rendering extension. The XML generated by this extension can be imported into a database, used as an XML data message, or sent to a custom application.
For more information, see Exporting to XML (Report Builder and SSRS).
The Atom rendering extension generates Atom-compliant data feeds from reports. The data feeds are readable and exchangeable with applications such as the SQL Server 2016 Power Pivot client that can consume Atom-compliant data feeds.
The output is an Atom service document that lists the data feeds available from a report. At least one data feed is created for each data region in a report. Depending on the type of data region and the data that the data region displays, multiple data feeds might be generated.
For more information, see Generating Data Feeds from Reports (Report Builder and SSRS).
To export a report, run the report in Report Manager or Report Builder and then select a format from the Export drop-down list. You are prompted to choose whether to save or open the file. If you chose Open, the report opens in the application associated with the rendering format you chose. (For example, when you select Excel the report opens in Excel). If you chose Save, the report is saved. For example, if you are exporting to Excel, the report is saved as an .xls file. The file associations defined for the local computer determine which application is used for a particular rendering format. For more information, see Export a Report as Another File Type (Report Builder and SSRS).
The report server exports the report as it is in the current user session. If someone publishes an updated version of the report while you have the report open or the data that the report displays changes, the exported report is not updated.
Report pagination might be affected when you export a report to a different format. When you preview a report, you are viewing the report as it is rendered by the HTML rendering extension, which follows soft-page break rules. When you export a report to a different file format, such as Adobe Acrobat (PDF), pagination is based on the physical page size, which follows hard-page break rules. Pages can also be separated by logical page breaks that you add to a report, but the actual length of a page varies based on the renderer type that you use. To change the pagination of your report, you must understand the pagination behavior of the rendering extension you choose. You might need to adjust the design of your report layout for this rendering extension. For more information see, Page Layout and Rendering (Report Builder and SSRS).
To generate data feeds from a report, run the report in Report Manager, and then click the Generate Data Feed icon on the Report Manager toolbar. You are prompted to choose whether to save or open the file. If you chose Open, the Atom service document opens in the application that is associated with the .atomsvc file extension. If you chose Save, the document is saved as an .atomsvc file. By default, the name of the file is the name of the report. You can change the name to one that is more meaningful.
You save the Atom service document to your computer. Later you can upload it to a report server or another server to make it available for others to use. For more information, see Generating Data Feeds from Reports (Report Builder and SSRS) and Generate Data Feeds from a Report (Report Builder and SSRS).
Sometimes your reports look different or do not work the way you want after you export them to a different format. This occurs because certain rules and limitations might apply to the renderer. You can address many limitations by considering them when you create the report. You might need to use a slightly different layout in your report, carefully align items within the report, confine report footers to a single line of text, and so forth.
If your report contains Unicode text with Arabic numbers, or contains dates in Arabic, the dates and numbers do not render correctly when you export the report to any of the following formats or print the report.
If you export the report to HTML, the dates and numbers render correctly.
The topics about specific renderers describe how report items and data regions are rendered as well as the limitations and solutions for each renderer.
Reporting Services provides additional features to help you create reports that work well in other formats. Page breaks on tablix data regions (table, matrix, and list), groups, and rectangles give you better control of report pagination. Report pages, delimited by page breaks, can have different page names and reset page numbering. By using expressions, the page names and page numbers can be dynamically updated when the report is run. For more information, see Pagination in Reporting Services (Report Builder and SSRS).
In addition, you can use the RenderFormat built-in global to conditionally apply different report layouts for different renderers. For more information, see Built-in Globals and Users References (Report Builder and SSRS).
Exporting a report is an on-demand task that you perform when the report is open in Report Manager or Report Builder. If you want to automate an export operation (for example, to export a report to a shared folder as a specific file type on a recurring schedule), create a subscription that delivers the report to a shared folder. For more information, see File Share Delivery in Reporting Services.
Reports previewed in the reporting tools or opened in a browser application such as Report Manager are always first rendered in HTML. You cannot specify a different rendering extension as the default for viewing. You can, however, create a subscription that produces a report in the rendering format you want for subsequent delivery to an e-mail inbox or shared folder. For more information, see Create and Manage Subscriptions for Native Mode Report Servers and Create, Modify, and Delete Data-Driven Subscriptions.
You can also access a report through a URL that specifies a rendering extension as a URL parameter and render the report directly to the specified format without rendering it in HTML first. The following example renders a report in Excel format:
For more information, see Export a Report Using URL Access.