09/10/2012 12:08:51

The most up-to-date version of this file is available online at the Microsoft Download Center:

Contents

Copyright Notice

The information provided in this document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. ©2012 Microsoft.  All rights reserved.Access, Microsoft SharePoint are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.

Background

What’s New in This Release

SharePoint integration has been re-architected to greatly improve the SharePoint IT administrator experience, the end user experience, and supportability. The new architecture is implemented as a SharePoint shared service. The Shared service architecture allows Reporting Services to leverage many of the IT features of SharePoint products. The following is a list of some of the benefits from this release:

  • Configuration of Reporting Services with SharePoint is now completely through SharePoint Central Administration using management pages for Reporting Services service applications or using Reporting Services SharePoint mode PowerShell cmdlets.

  • Leverage SharePoint scale-out functionality for Reporting Services Service Applications.

  • The new Reporting Services shared service is hosted in SharePoint Shared Service Application pool.

  • The new Reporting Services service applications support Claims based authentication.

  • SharePoint cross-farm support for viewing reports.

  • Support for SharePoint backup and recovery and end-to-end SharePoint ULS logging.

  • Power View, a feature of SQL Server 2012 Reporting Services Add-in for Microsoft SharePoint Enterprise Edition is an interactive data exploration, visualization, and presentation experience. It provides drag-and-drop ad hoc reporting for business users such as data analysts, business decision makers, and information workers. Power View reports are in a new file format, RDLX.

  • Reporting Services data alerting is a data-driven alerting solution that informs you about changes in report data that are of interest to you at a relevant time. The following summarizes the key areas of data alerting:

    • Define and save alert definitions—User views a report, creates rules that identify interesting data values, defines recurrence patterns for sending the alert, and specifies the recipients of the alert message.

    • Run alert definitions—Alerting service runs alert definitions at a scheduled time, retrieves report data, and triggers alerts based on rules in alert definition.

    • Deliver alerts to recipients—Alerting service creates an alert instance and sends email messages to recipients.

[Top]

Requirements and Supported Combinations

To install the Reporting Services Add-in, the computer must meet the following software requirements in addition to the software and hardware requirements of the SharePoint product you integrate with:

  • Microsoft Windows Installer 3.0 or newer.

  • SharePoint Foundation 2010, SharePoint Server 2010, or SharePoint Server 2013. The SQL Server 2012 Add-in is not supported on earlier versions of Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server2007.

  • The add-in is 64-bit only, which is a requirement of SharePoint products and technologies.

  • Important

    Not all Reporting Services features are supported in all combinations of:

    • The version of the report server.

    • The version of the Reporting Services add-in for SharePoint.

    • The version of SharePoint.

    For more information, see the following:

[Top]

Domain user account requirements for SharePoint administration and services

A deployment of a SharePoint server uses a variety of accounts to run services and access front-end and back-end servers. If you specify domain accounts for your deployment, you should follow best practice recommendations and specify accounts that are used exclusively by the SharePoint Web application. Do not configure a service account to run under the domain user account of an actual person who will access the SharePoint site.

A domain account is required if:

  • The SharePoint site and the report server are on different computers.

  • The SharePoint site is hosted in an application pool that runs as a built-in account, such as NetworkService.

SharePoint 2010 products and technologies require domain accounts for service configuration like reporting services SharePoint integration. For more information about service account requirements and recommendations, see Initial deployment administrative and service accounts (SharePoint Server 2010) in the SharePoint product and technology documentation.

[Top]

Installing the add-in

To install the Reporting Services Add-in, you must be an administrator on the computer and a member of the SharePoint Farm Administrators group. In a SharePoint farm deployment, the add-in must be installed on each Web front-end server (WFE).

The add-in follows SharePoint pre-deployment standards and installs files in locations used by the SharePoint installation. Setup creates folders under the following path and copies files to the folders:

%program files%\common files\Microsoft Shared\Web Server Extensions\14\

or

%program files%\common files\Microsoft Shared\Web Server Extensions\15\

The add-in can be installed using one of the following methods.

For more information, see Install or Uninstall the Reporting Services Add-in for SharePoint (http://technet.microsoft.com/en-us/library/aa905871.aspx).

[Top]

Upgrade

If you have an existing installation of the Reporting Services Add-in, you can upgrade to the current version. Setup will remove the older version of the add-in and then the new version will be installed.

Note that the Reporting Services Add-in is not instance-aware. You can only have one instance of the add-in on a computer. You cannot different versions side-by-side.

[Top]

Installation Order

The exact steps that you take to install and configure the Reporting Services Add-in as part of a SharePoint server deployment may vary depending on your requirements and the order that you install the different technologies.

Note

The add-in can be installed before installing a SharePoint product or after SharePoint installation. The advantage of installing the add-in prior to the SharePoint product or technology is that as new servers are added to the farm, the Reporting Services Add-in will be configured and activated by the SharePoint farm.

For more information related to SharePoint 2013, see the following:

For more information related to SharePoint 2010, see the following:

[Top]

Existing SharePoint farm

To install and configure Reporting Services on an existing SharePoint farm, do the following step-by-step procedures in this order:

  1. Install the SharePoint add-in on all Web front-end (WFE) computers.

  2. Install SQL Server 2012 Reporting Services and the Database engine.

  3. Create at least one Reporting Services service application and configure service application association.

  4. Add Reporting Services content types to your document library

  5. Verify SQL Server Agent is running and provisioned. For more information, see Provision Subscriptions and Alerts for SSRS Service Applications (http://technet.microsoft.com/library/hh231725(SQL.110).aspx).

  6. Configure e-mail settings for your service application.

  7. For reports with data external to the SharePoint farm and requiring Windows Integrated credentials, ensure the SharePoint Claims to Windows Token shared service (C2WTS) is configured to allow access to the external data sources. For more information on C2WTS, see Claims to Windows Token Service (C2WTS) (http://go.microsoft.com/fwlink/?LinkId=231169).

Single Server Installation

To install and configure Reporting Services with SharePoint on a single computer, do the following step-by-step procedures in this order:

  1. Install Database Engine, Reporting Services, and the Reporting Services add-in for SharePoint. Verify that you have a valid installation before you install the SharePoint Product.

  2. Run the SharePoint Products Preparation tool.

  3. Install SharePoint Server or SharePoint foundation.

  4. Run the SharePoint Products Configuration Wizard. Then open the SharePoint site to verify you have a valid installation.

  5. Run the SharePoint Farm Configuration wizard.

  6. Install and Start the Reporting Services Shared Service.

  7. Create at least one Reporting Services service application and configure service application association.

  8. Add Reporting Services content types to your document library.

  9. Verify SQL Server Agent is running and provisioned. For more information, see Provision Subscriptions and Alerts for SSRS Service Applications (http://msdn.microsoft.com/en-us/library/hh231725.aspx).

  10. Configure e-mail for your service application.

  11. For reports with data external to the SharePoint farm and requiring Windows Integrated credentials, ensure the SharePoint Claims to Windows Token shared service (C2WTS) is configured to allow access to the external data sources. For more information on C2WTS, see Claims to Windows Token Service (C2WTS) (http://go.microsoft.com/fwlink/?LinkId=231169).

Getting Help

For help with SQL Server technical issues not related to documentation, see Getting Assistance with SQL Server (http://go.microsoft.com/fwlink/?LinkId=74357).

For the most recent release notes, see SQL Server 2012 Release Notes (http://go.microsoft.com/fwlink/?LinkId=196445).

For the most recent troubleshooting information, see the following TechNet wiki article Troubleshoot SQL Server Reporting Services (SSRS) in SharePoint Integrated Mode (http://go.microsoft.com/fwlink/?LinkId=207239).

[Top]