Local Mode vs. Connected Mode Reports in the Report Viewer (Reporting Services in SharePoint Mode)
Applies To: SQL Server 2016
Reporting Services reports can be configure to run in either local mode or connected mode, which leverages a Reporting Services report server. Instead, you can use the Report Viewer to directly render reports from SharePoint when the data extension supports local mode reporting. This approach is called local mode. In previous versions of Reporting Services, the SharePoint farm was required to be connected to a Reporting Services report server configured in SharePoint mode so the Report Viewer control could render reports. This approach is called remote mode or connected mode.
In local mode there is no Reporting Services report server. You must install the Reporting Services add-in for SharePoint products, but no Reporting Services report server is required. With Local mode, users can view reports but will not have access to server side features such as subscriptions and data alerts.
|Applies to: Reporting Services SharePoint mode|
In this topic:
Local mode: When you have a data extension that supports local mode, the Report Viewer directly renders reports from SharePoint. In local mode there is no Reporting Services report server. You must install the Reporting Services add-in for SharePoint products, but no Reporting Services report server is required. With Local mode, users can view reports but will not have access to server side features such as subscriptions and data alerts.
Connected mode, also called remote mode requires a Reporting Services report server in SharePoint mode, connected to the SharePoint farm so the Report Viewer control could render reports..
The following is a list of the data processing extensions that support local mode reporting:
Microsoft Access 2010 reporting extension. For more information on Access Services, see Use Access Services with SQL Reporting Services: Installing SQL Server 2008 R2 Reporting Services Add-In (SharePoint Server 2010).
The Reporting Services SharePoint list data extension. For more information on the SharePoint List Data Extension, see Data Sources Supported by Reporting Services (SSRS)
Custom data processing extensions can also be developed to support local mode. For more information, see Implementing a Data Processing Extension.
Local mode supports rendering reports that have an embedded data source or a shared data source from an .rsds file. However, you cannot manage the report or its associated data source. If you try to do this, you will receive an error that this is not supported in local mode. Managing data sources in the SharePoint site is supported in only connected mode.
You can configure your SharePoint 2013 farm to support existing Access 2010 web databases and Reporting Services local mode. For more information, see Set up and configure Access Services 2010 for web databases in SharePoint Server 2013.
It is not possible to create new Access web databases for SharePoint 2013. Access 2013 uses a new type of database, Access web app that you build in Access, then use and share with others as a SharePoint app in a web browser.
For more information, see the following.
What's new in Access 2013 (http://office.microsoft.com/access-help/what-s-new-in-access-2013-HA102809500.aspx).
Basic tasks for an Access app (http://office.microsoft.com/access-help/basic-tasks-for-an-access-app-HA102840210.aspx?CTT=5&origin=HA102809500).
Local mode requires ASP.NET session state. The installation of Access services will enable ASP.Net sessions state. You can also enable using PowerShell.
Open the SharePoint 2010 Management Shell.
Type the following command:
When prompted, type the name of your database.
Perform an IIS reset.
For the latest information on using ADS extension with Reporting Services connected mode, see Access Services Report in SharePoint Site shows error in data extension ‘ADS’.