Rediger

Del via

Upgrade Reports (SSRS)

  • Artikkel

Applies to:  SQL Server 2016 (13.x)  Power BI Report Server

Report definition (.rdl) files are automatically upgraded in the following ways:

  • When you open a paginated report in Report Designer in SQL Server Data Tools (SSDT), the report definition is upgraded to the currently supported RDL schema. When you specify a SQL Server 2008 (10.0.x), SQL Server 2008 R2 (10.50.x), SQL Server 2012 (11.x), or SQL Server 2014 (12.x) report server in the project properties, the report definition is saved in a schema that is compatible with the target server.

  • When you upgrade a Reporting Services installation to a SQL Server 2016 (13.x) Reporting Services or later (SSRS) installation, existing reports and snapshots that have been published to a report server are compiled and automatically upgraded to the new schema the first time they are processed. If a report cannot be automatically upgraded, the report is processed using the backward-compatibility mode. The report definition remains in the original schema.

After a report is upgraded locally or on the report server, you might notice additional errors, warnings, and messages. This is the result of changes to the internal report object model and processing components, which cause messages to appear when underlying problems in the report are detected. For more information, see Reporting Services Backward Compatibility.

For more information about new features for SQL Server 2016 (13.x) Reporting Services or later (SSRS), see What's new in SQL Server Reporting Services (SSRS).

Versions Supported by Upgrade

Reports that were created in any previous version of Reporting Services can be upgraded. This includes the following versions:

  • SQL Server 2008 (10.0.x)

  • SQL Server 2008 R2 (10.50.x)

  • SQL Server 2012 (11.x)

  • SQL Server 2014 (12.x)

Report Definition (.rdl) Files and Report Designer

A report definition file includes a reference to the RDL namespace that specifies the version of the report definition schema that is used to validate the .rdl file.

When you open an .rdl file in Report Designer in SQL Server Data Tools (SSDT), if the report was created for a previous namespace, Report Designer automatically creates a backup file and upgrades the report to the current namespace. This is the only way you can upgrade a report definition file.

Deployment properties that you set can affect which schema the report definition file is saved in. For more information, see Deployment and Version Support in SQL Server Data Tools (SSRS).

You can upload an .rdl file created in an earlier version of Reporting Services to the new version and it is automatically upgraded on first use. The report server stores the report definition file in the original format. The report is automatically upgraded the first time it is viewed, but the stored report definition file remains unchanged.

To identify the current RDL schema for a report, for a report server, or for Report Designer, see Find the Report Definition Schema Version (SSRS).

Published Reports and Report Snapshots

On first use, the report server tries to upgrade existing published reports and report snapshots to the new report definition schema, requiring no specific action on your part. When a user views a report or a report snapshot, or when the report server processes a subscription, the upgrading attempt occurs. The report definition is not replaced but continues to be stored on the report server in its original schema. If a report cannot be upgraded, the report runs in backward-compatibility mode.

Backward-Compatibility Mode

A report that is successfully upgraded is processed by the SQL Server 2016 (13.x) Reporting Services or later (SSRS) report processor. A report that cannot be upgraded is processed by the SQL Server 2008 (10.0.x), SQL Server 2008 R2 (10.50.x), SQL Server 2012 (11.x), or SQL Server 2014 (12.x) Reporting Services report processor in backward-compatibility mode. A report cannot be processed by both report processors. On first use, a report is either successfully upgraded or marked for backward compatibility.

Only the SQL Server 2016 (13.x) Reporting Services or later (SSRS) report processor supports new features. If a report cannot be upgraded, you can still view the rendered report but new features are not available. To take advantage of the new features, a report must be successfully upgraded.

Upgrading a Report with Subreports

When a report contains subreports, one of four possible states can occur during upgrade:

  • The main report and all subreports can be successfully upgraded. They are processed by the SQL Server 2016 (13.x) Reporting Services or later (SSRS) report processor.

  • The main report and all subreports cannot be upgraded. They are processed by the SQL Server 2008 (10.0.x), SQL Server 2008 R2 (10.50.x), SQL Server 2012 (11.x), or SQL Server 2014 (12.x) Reporting Services report processor.

  • The main report can be upgraded but one or more subreports cannot be upgraded. The main report is processed by the SQL Server 2016 (13.x) Reporting Services or later (SSRS) report processor, but the rendered report shows the message "Error: Subreport could not be processed" in the location where the subreport that could not be upgraded would appear.

  • The main report cannot be upgraded but one or more subreports can be upgraded. The main report is processed by the SQL Server 2016 (13.x) Reporting Services or later (SSRS) report processor, but the rendered report shows the message "Error: Subreport could not be processed" in the location where the subreport would appear.

If you see the error "Error: Subreport could not be processed", you must change the definition of the main report or the subreport so that the reports can be processed by the same version of the report processor.

Drillthrough reports do not have this limitation because they are processed as independent reports.

Upgrading a Report with Custom Report Items

SQL Server 2008 (10.0.x), SQL Server 2008 R2 (10.50.x), SQL Server 2012 (11.x), or SQL Server 2014 (12.x) Reporting Services reports might contain custom report items (CRIs) provided by third-party software vendors and installed by the system administrator on the report authoring computer and the report server. Reports that contain CRIs can be upgraded in the following ways:

  • A SQL Server 2008 (10.0.x), SQL Server 2008 R2 (10.50.x), SQL Server 2012 (11.x), or SQL Server 2014 (12.x) Reporting Services report server is upgraded to a SQL Server 2016 (13.x) Reporting Services or later (SSRS) report server. Published reports on the report server are automatically upgraded on first use.

  • A SQL Server 2008 (10.0.x), SQL Server 2008 R2 (10.50.x), SQL Server 2012 (11.x), or SQL Server 2014 (12.x) Reporting Services report is uploaded to a SQL Server 2016 (13.x) Reporting Services or later (SSRS) report server. The report is automatically upgraded on first use.

  • A SQL Server 2008 (10.0.x), SQL Server 2008 R2 (10.50.x), SQL Server 2012 (11.x), or SQL Server 2014 (12.x) Reporting Services report is opened in Report Designer in SQL Server Data Tools (SSDT). A backup copy of the original report is created. One of the following two cases occurs:

    1. All CRIs in the report have no unsupported features. The CRIs are converted to report items in the new report definition schema, so the entire report is upgraded. If you save the file, it is saved in the current RDL namespace.

    2. One or more CRIs in the report have unsupported features. A dialog box prompts the user whether to convert the CRIs are leave them unchanged.

    For more information, see Opening a Report in Report Designer later in this topic.

For information about identifying the current RDL namespace for a report server, SQL Server Data Tools, or a report, see Find the Report Definition Schema Version (SSRS).

Upgrading Reports on a Report Server

The first time a SQL Server 2008 (10.0.x), SQL Server 2008 R2 (10.50.x), SQL Server 2012 (11.x), or SQL Server 2014 (12.x) Reporting Services report runs on a report server that has been upgraded to a SQL Server 2016 (13.x) Reporting Services or later (SSRS) report server, the report is automatically upgraded to the current report definition namespace supported by the report server. The report could have existed on the report server before the upgrade, or the report could have been uploaded via the web portal or published to the report server from Report Designer in SQL Server 2008 (10.0.x), SQL Server 2008 R2 (10.50.x), SQL Server 2012 (11.x), or SQL Server 2014 (12.x) SQL Server Data Tools.

The following table lists the upgrade action that is performed by the report server for specific types of CRIs in a report.

CRI type Report Server upgrade action
Third-party CRIs Upgrade not performed.

Processed by the SQL Server 2008 (10.0.x), SQL Server 2008 R2 (10.50.x), SQL Server 2012 (11.x), or SQL Server 2014 (12.x) Reporting Services report processor.

Opening a Report with CRIs in Report Designer

When you open a SQL Server 2008 (10.0.x), SQL Server 2008 R2 (10.50.x), SQL Server 2012 (11.x), or SQL Server 2014 (12.x) Reporting Services report with CRIs in Report Designer in SQL Server Data Tools (SSDT), the report will be upgraded to the new report definition schema. Depending on the CRIs contained in the report, one of the following actions will take place:

  • Third-party CRIs detected. If the version of the CRI that is installed on the report authoring computer is not compatible with the new RDL schema, the design surface shows a text box with a red X. You must contact your system administrator to install new versions of the CRI from third-party vendors that are compatible with the new RDL schema.

Saving a report after it is upgraded in the report authoring environment is the only way to upgrade an existing report to the new report definition schema.

Convert CRI Dialog Box

This report contains custom report items (CRIs) with unsupported features. CRIs are extensions to the Report Definition Language (RDL) that support custom objects that display data in a report. CRIs include design-time and run-time components that are supplied by third-party software vendors.

Note

Choosing to support custom report items on a report server is a decision made by the system administrator. To view CRIs in a report, the CRI components must be installed on the report authoring client to preview a report and on the report server to view a published or uploaded report. For more information, see Custom Report Items and documentation from the third-party software vendor.

Some CRIs can be converted to report items in the new report definition format. Use the following list to decide whether to convert the CRIs in this report:

  • Yes Choose Yes to convert all the CRIs in the report, where possible. Unsupported features in the CRIs cannot be upgraded and are removed from the report definition file. When you view the report, you might see differences in the way the CRI displays in the report.

  • No Choose No when you do not want to convert the CRIs in the report. These CRIs cannot be displayed by the report processor in their current version. If your system administrator is planning to install a new version of the CRI from the third-party software vendor that is compatible with the new report definition format, you should choose No. Until new versions are available, the CRIs display in the report as an empty text box with a red X.

In either case, the report is upgraded to the new report definition format and a backup copy of the original report is saved as <Report Name> - Backup.rdl. If you save the report in your report authoring tool, you are saving the upgraded report in the new report definition format. If you publish the report, the report is first saved on your computer, and then published to the report server. You are publishing the upgraded version of the report to the report server.

If you do not save the report, the original report remains unchanged. However, you cannot edit this report in the SQL Server 2016 version of SQL Server Data Tools or a report authoring environment that uses a newer report definition format. You can continue to run the original version of the report by uploading it to a SQL Server 2016 (13.x) Reporting Services or later (SSRS) report server by using the web portal. For more information, see Web Portal.

For reports that you upload instead of publish to a report server, the report processor determines whether the report can be upgraded on first use. Reports that cannot be upgraded are processed in backward-compatibility mode, and continue to display as they did in the earlier version of Reporting Services.

Related content