| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | ms.custom | helpviewer_keywords | |||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Breaking changes in SQL Server Reporting Services in SQL Server 2016 |
Learn about changes in Reporting Services that might break applications, scripts, or functionalities based on earlier versions of SQL Server. |
maggiesMSFT |
maggies |
07/02/2017 |
reporting-services |
reporting-services |
conceptual |
updatefrequency5 |
|
[!INCLUDE ssrs-appliesto] [!INCLUDE ssrs-appliesto-2016] [!INCLUDE ssrs-appliesto-not-2017] [!INCLUDE ssrs-appliesto-not-pbirs]
[!INCLUDE ssrs-previous-versions]
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.
Custom security extensions need some modification to work with the new [!INCLUDEssRSWebPortal]. Security extensions need to use the IAuthenticationExtension2 interface.
The [!INCLUDEssRSWebPortal] application name changes from "ReportManager" to "ReportServerWebApp".
- Behavior changes to SQL Server Reporting Services in SQL Server 2016
- What's new in Reporting Services (SSRS)
- Deprecated features in SQL Server Reporting Services in SQL Server 2016
- Discontinued functionality to SQL Server Reporting Services in SQL Server 2016
More questions? Try asking the Reporting Services forum