| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | ms.custom | monikerRange |
|---|---|---|---|---|---|---|---|---|---|
Integrating into applications |
Reporting Services is an open and extensible reporting platform designed to provide developers with a comprehensive set of APIs for developing solutions. |
maggiesMSFT |
maggies |
05/14/2019 |
reporting-services |
application-integration |
reference |
updatefrequency5 |
= sql-server-2016 |
[!INCLUDE ssrs-appliesto] [!INCLUDEssrs-appliesto-2016] [!INCLUDEssrs-appliesto-not-2017] [!INCLUDE ssrs-appliesto-not-pbirs]
[!INCLUDEssRSnoversion] is an open and extensible reporting platform designed to provide developers with a comprehensive set of APIs for developing solutions.
Note
Starting with SQL Server 2017 Reporting Services, REST API access is available for developing solutions. SOAP API access has been deprecated. For more information, see Develop with the REST APIs for Reporting Services.
There are three options for integrating [!INCLUDEssRSnoversion] into custom applications: the Report Server Web service, also known as the [!INCLUDEssRSnoversion] SOAP API, the Report Viewer controls for [!INCLUDEmsCoName] [!INCLUDEvsprvs], and URL access. Each option provides a different approach for integrating [!INCLUDEssRSnoversion] into your applications.
The Report Server Web service is the primary interface for developing against [!INCLUDEssRSnoversion]. Whether you're developing code to manage your report catalog or developing code to render reports to a supported format, the Web service exposes all the necessary methods to integrate [!INCLUDEssRSnoversion] into your applications. An example of one such application is the web portal, which is included with [!INCLUDEssRSnoversion]; it uses the Web service to manage the report server database.
The Report Viewer controls available for [!INCLUDEvsprvs] are used for integrating report viewing into your applications. There are two controls: one for Windows Forms-based applications and one for Web Forms applications. Each control provides the capability for viewing reports that are deployed to a report server. Each control also allows you to render reports that exist in an environment where a report server isn't installed.
URL access is another option for integrating report viewing into your applications if the Report Viewer controls aren't an option. In addition, URL access is useful for sending links to reports to users via e-mail.
Integrating Reporting Services by using SOAP
Describes how to integrate [!INCLUDEssRSnoversion] report navigation and management into your existing business applications using the Report Server Web service.
Integrating Reporting Services by using the Report Viewer controls
Describes how to integrate report viewing into your existing applications using the Report Viewer controls.
Integrating Reporting Services by using URL access
Describes how to integrate [!INCLUDEssRSnoversion] report navigation into your existing business applications using URL access.
For deciding on using URL access or the SOAP APIs, see Choosing between URL access and SOAP in Reporting Services.
For information on the SQL Server 2017 Reporting Services REST API, see Develop with the REST APIs for Reporting Services.
More questions? Try asking the Reporting Services forum