Breaking Changes in SQL Server Reporting Services in SQL Server 2016
This topic describes breaking changes in Reporting Services. These changes might break applications, scripts, or functionalities that are based on earlier versions of SQL Server. You might encounter these issues when you upgrade, or in custom scripts or reports.
In this topic:
There are no Reporting Services breaking changes in SQL Server 2014.
You cannot browse or reference directly to the Report Server using the virtual directly name in the URL path. For example:
It is now required that you include the SharePoint site in the URL path. For example, if your site name is ‘videos’ and used the ‘sites’ prefix, the URL would look similar to the following:
The input setting /RSINSTALLMODE only works with Native mode installations and it does not work for SharePoint mode installations. For example, the following is not supported in SQL Server 2016: /RSINSTALLMODE="DefaultSharePointMode”. In place of that input setting, use /RSSHPINSTALLMODE="DefaultSharePointMode".
The following statement is an example of a complete installation command and parameter set: setup /ACTION=install /FEATURES=SQL,RS /InstanceName=Denali_INST1 …. /RSSHPINSTALLMODE="DefaultSharePointMode"
For more information on command-line installations, see Command Prompt Installation of Reporting Services SharePoint Mode and Native Mode.
The Configuration of Reporting Services SharePoint is now completed using PowerShell cmdlets and SharePoint Central Administration. The new Reporting Services SharePoint mode architecture utilizes the SharePoint services architecture. SharePoint does not support WMI interfaces.
These changes affect the following list of components and work flows:
Custom applications that use the Reporting Services WMI provider for Reporting Services in SharePoint mode.
The Reporting Services Configuration Manager, rskeymgmt.exe, and rsconfig.exe. Instead of using those utilities for configuration of Reporting Services SharePoint mode, use SharePoint Central Administration and PowerShell.
SQL Server Management Studio: Customers cannot reference a server with syntax similar to <machine_name>/<instance_name>. Starting with the SQL Server 2008 release, the recommended method was to use a SharePoint site URL. For example, http://<sharepoint_server>/<sharePoint_site>. Starting with SQL Server 2012, a SharePoint site URL is the only supported syntax.
SQL Server Data Tools (SSDT) no longer supports report model projects. The Report Model designer is not available in SQL Server 2016 Reporting Services (SSRS). You cannot create new Report Model projects or open existing projects in SQL Server Data Tools (SSDT) and you cannot create or update report models. To update report models, you can use SQL Server 2008 R2 Reporting Services or earlier tools. You can continue to use report models as data sources in reports authored in SQL Server 2016 Reporting Services (SSRS) tools such as Report Builder and Report Designer. The query designer that you use to create queries to extract report data from report models continues to be available in SQL Server 2012 Reporting Services.
This section describes breaking changes in SQL Server 2008 R2 Reporting Services.
Because SQL Server 2008 R2 is a minor version upgrade of SQL Server 2008, we recommend that you also review the content in the SQL Server 2008 section.
In SQL Server 2008 R2 Reporting Services, the CSV file includes chart and gauge data. Applications that depend on a previous CSV file structure will no longer work because of the additional columns for charts and gauges.
For more information, see Exporting to a CSV File (Report Builder and SSRS).