Export (0) Print
Expand All

Behavior Changes to SQL Server Reporting Services in SQL Server 2014

This topic describes behavior changes in Reporting Services. Behavior changes affect how features work or interact in SQL Server 2014 as compared to previous versions of SQL Server.

In this topic:

There are no Reporting Services behavior changes in SQL Server 2014.

This section describes behavior changes to Reporting Services SharePoint mode.

View Items permission will not download Shared Datasets (SharePoint Mode)

New Behavior: Users with the SharePoint permission of “View Items” can no longer download the contents of Reporting Services shared datasets. This behavior change is now consistent with the “View Items” permissions for reports, data sources, and models. Users with “View Items” permission can view and execute reports, data sources, and models but they cannot download their content.

Previous Behavior: Users with the “View Items” SharePoint permission could download the contents of Reporting Services shared datasets.

For more information on SharePoint permission levels, see User permissions and permission levels

Report Server trace logs are in a new location for SharePoint mode (SharePoint Mode)

New behavior: For a report server installed in SharePoint mode, the report server trace logs will be under %Programfiles%\Common Files\Microsoft Shared\Web Server Extensions\14\Web Services\ReportServer\LogFiles.

Previous Behavior: Report Server trace logs were found under a path similar to the following: %Programfilesdir%\Microsoft SQL Server\<RS_instance>\Reporting Services\LogFiles

GetServerConfigInfo SOAP API is no longer supported (SharePoint Mode)

New behavior: Use PowerShell cmdlet “Get-SPRSServiceApplicationServers”

Previous Behavior: Customers could develop SOAP client code to communicate directly with the Reporting Services end point, and call GetReportServerConfigInfo().

Report Server Configuration and Management Tools

Configuration Manager is not used for SharePoint Mode

New behavior: The Reporting Services Configuration Manager no longer supports SharePoint Mode report servers. Configuration of Reporting Services SharePoint mode can now be completed by using SharePoint Central administration and therefore Reporting Services Configuration Manager no longer supports SharePoint mode. Configuration Manager is now only used for Native mode report servers.

You cannot change the server from one mode to another

New behavior: You cannot change server modes. If you install a report server as Native mode you cannot change or re-configure it to be SharePoint mode. If you install in SharePoint mode, you can change the report server to native mode.

Previous Behavior: Customer installs a Reporting Services report server in SharePoint mode. If the customer wants to switch the report server to Native mode, they could open the Reporting Services configuration manager to switch to Native mode by either creating a new or connecting to an existing Native mode database. The customer could also use Reporting Services Configuration Manager to switch from SharePoint mode to Native mode.

Arrow icon used with Back to Top link Top

This section describes behavior changes in SQL Server 2008 R2 Reporting Services.

Note 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.

SecureConnectionLevel Property in the Reporting Services WMI Provider Library

In the WMI provider library for SQL Server 2008 Reporting Services, the SecureConnectionLevel property allows values of 0,1,2,3, with 0 indicating that Secure Socket Layer (SSL) is not required for any of the Web service methods, 3 indicating that SSL is required for all the Web service methods, and 1 and 2 indicate subsets of Web service methods that require SSL. In SQL Server 2008 Reporting Services, these values will have only two possible meanings:

  • 0 indicates SSL is not required for any of the Web service methods.

  • A positive integer indicates SSL is required for all the Web service methods.

This change affects how the report server responds to Web service calls. For example, ListSecureMethods now returns nothing if SecureConnectionLevel is set to 0 and all the methods in ReportingService2005 if SecureConnectionLevel is set to 1, 2, or 3.

Arrow icon used with Back to Top link Top

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft