Skip to content

breaking-changes-in-sql-server-reporting-services-in-sql-server-2016.md

Latest commit

 

History

History
81 lines (55 loc) · 6.89 KB

breaking-changes-in-sql-server-reporting-services-in-sql-server-2016.md

File metadata and controls

81 lines (55 loc) · 6.89 KB
title Breaking Changes in SQL Server Reporting Services in SQL Server 2014 | Microsoft Docs
ms.custom
ms.date 06/13/2017
ms.prod sql-server-2014
ms.reviewer
ms.technology reporting-services-native
ms.topic conceptual
helpviewer_keywords
Me.Value references
Reporting Services, backward compatibility
breaking changes [Reporting Services]
ms.assetid 39c7aafd-dcb9-4317-b8f7-d15828eb4f9a
author maggiesMSFT
ms.author maggies
manager kfile

Breaking Changes in SQL Server Reporting Services in SQL Server 2014

This topic describes breaking changes in [!INCLUDEssRSnoversion]. These changes might break applications, scripts, or functionalities that are based on earlier versions of [!INCLUDEssNoVersion]. You might encounter these issues when you upgrade, or in custom scripts or reports. For more information, see Use Upgrade Advisor to Prepare for Upgrades.

In this topic:

[!INCLUDEssSQL14] Reporting Services Breaking Changes

There are no [!INCLUDEssRSnoversion] breaking changes in [!INCLUDEssSQL14].

[!INCLUDEssSQL11] Reporting Services Breaking Changes

SharePoint Mode Server References Require the SharePoint Site

You cannot browse or reference directly to the Report Server using the virtual directly name in the URL path. For example:

http://<Server name>/ReportServer

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:

http://<Server Name>/sites/videos/_vti_bin/ReportServer

Changes to SharePoint Mode Command-Line Installation

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 [!INCLUDEssCurrent]: /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=/proxy/https/github.com/MicrosoftDocs/sql-docs/blob/e2c3003d4728ce29584144286df875611d95f6d4/docs/2014/reporting-services/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 Reporting Services WMI Provider no longer supports Configuration of SharePoint Mode

The Configuration of [!INCLUDEssRSnoversion] SharePoint is now completed using PowerShell cmdlets and SharePoint Central Administration. The new [!INCLUDEssRSnoversion] 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 [!INCLUDEssRSnoversion] WMI provider for [!INCLUDEssRSnoversion] in SharePoint mode.

  • The [!INCLUDEssRSnoversion] Configuration Manager, rskeymgmt.exe, and rsconfig.exe. Instead of using those utilities for configuration of [!INCLUDEssRSnoversion] 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 [!INCLUDEssKatmai] release, the recommended method was to use a SharePoint site URL. For example, http://<sharepoint_server>/<sharePoint_site>. Starting with [!INCLUDEssSQL11], a SharePoint site URL is the only supported syntax.

Report Model Designer is not available in SQL Server Data Tools

[!INCLUDEssBIDevStudioFull] no longer supports report model projects. The Report Model designer is not available in [!INCLUDEssRSCurrent]. You cannot create new Report Model projects or open existing projects in [!INCLUDEssBIDevStudioFull] and you cannot create or update report models. To update report models, you can use [!INCLUDEssKilimanjaro][!INCLUDEssRSnoversion] or earlier tools. You can continue to use report models as data sources in reports authored in [!INCLUDEssRSCurrent] 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 [!INCLUDEssSQL11][!INCLUDEssRSnoversion].

SQL Server 2008 R2 Reporting Services Breaking Changes

This section describes breaking changes in [!INCLUDEssKilimanjaro] [!INCLUDEssRSnoversion].

Note

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.

Expanded CSV Data Renderer

In [!INCLUDEssKilimanjaro] [!INCLUDEssRSnoversion], 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).

See Also

Behavior Changes to SQL Server Reporting Services in SQL Server 2014
What's New (Reporting Services)
Deprecated Features in SQL Server Reporting Services in SQL Server 2014
Discontinued Functionality to SQL Server Reporting Services in SQL Server 2014