Home » business connectivity services » Central Administration Settings for Creating and Configuring Reporting Services as a SharePoint Server 2013 Service

Central Administration Settings for Creating and Configuring Reporting Services as a SharePoint Server 2013 Service

The task of adding the SQL Server 2012 SP1 Reporting Services for SharePoint service is best performed by SharePoint administrators.

Jason Himmelstein’s presentation in the first part of his series on Reporting Services, REPORTING SERVICES IN SHAREPOINT 2013 PART 1 is tailored for an audience of administrators. As we noted in the previous post to this blog, in this video he demonstrates how to use Power Shell to add this service. In the final few moments of the video he demonstrates how to use Central Administration to configure this service, though he still recommends Power Shell as the best method of adding Reporting Services as a SharePoint Server 2013 service.

Points administrators will likely want to remember include:

  1. A Service Application is required for any Web App. “So its one to one, one web app to one Reporting Services service application” It is not possible to create one Reporting Services service application for multiple web apps
  2. Better not to use the “nice long GUID” included in the “Database Name” data field on the “Create SQL Server Reporting Services Service Application” Dialog. Database Administrators are challenged by GUIDs. If it’s important to make DBAs feel comfortable, then better skip this option
  3. As he mentioned in one of the first tutorials in this series, it’s not possible to run Reporting Services “native” alongside “SharePoint Reporting Services” on the same core, so if the plan is to run both versions, then separate servers will have to be allocated for each.
  4. The only reason for a single server install of this service is for development and testing purposes, only. One web apps go to production, separate servers will have to be implemented.

Jason instructs the viewer to check out the “System Settings” for this new SharePoint Server 2013 service. He recommends using “SQL Compression” for “Snapshot Compression”. He also recommends enabling “Execution Logging”, and “Remote Errors”. The “Report Builder Download” should be set, by default.

Ira Michael Blonder

© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved