SharePoint 2010 and SSRS 2008 R2 Integration Improvements

Many organizations might be debating why they need to upgrade their existing MOSS 2007 and SSRS 2005/SSRS 2008 investments to the SharePoint 2010 and SSRS 2008 R2. This post highlights the latest improvements in the SharePoint-SSRS integration.

SharePoint 2010 – SSRS 2008 R2 integration improvements

  • Supports three Modes – Requires SSRS Add-in installed on SharePoint farm for all three modes.
    • Local Mode – Not required SSRS Server, You can upload the RDL file, create data sources directly from SharePoint but you can’t manage them, used by Access Services and native list reporting.
    • Connected Mode – Required SSRS Server – Native Mode and Integrated Mode.
  • Supports the SharePoint Multiple-Zones and AAM – Use the alternate access mapping functionality in your SharePoint environment to access report server items from one or more SharePoint zones (default, internet, intranet, extranet, or custom). This is useful when you have a SharePoint environment that can be accessed by users from multiple zones. It means while referencing the SSRS reports in the Report Viewer Web Part, no need to configure fully qualified URL, relative URL would work fine.
  • AJAX enabled Report Viewer Controls
  • Improved SSRS Add-in – Removed additional hop between Report viewer UI and Proxy, Support for the ULS logging
  • Supports for the Claims based Authentication
  • Allow Installation of RS Add-in as SharePoint 2010 pre-requisite installer. This is required component for the Access Services and List Reports. SSRS is the reporting engine for Access Services reporting – Access reports stored as RDL files in the Sharepoint.

SSRS 2008 R2, BIDS 2008 R2, Report Builder 3.0 Improvements

  • Powerful visualizations including map, sparklines, and tablix – SSRS 2008 introduced tablix and guage controls, SSRS 2008 R2 introduces the maps, sparklines, data bars, and indicator controls.
  • Self-service Grab ‘n Go Reporting using the Report Parts –  Allows endusers to create the report mash-ups. Sharing and reusing report parts common report elements helps to accelerate report creation, cut down costs, and increase end-user adoption.
  • Shared Data Sets
  • Native support for Reporting on SharePoint Lists – SharePoint Lists as a data source, Query designer in BIDS and RB 3.0 supoorts the visual drag and drop of list columns to design the query. No need to write complex SOAP and CAML queries to retrieve the data from the SharePoint Web Service as a XML data source. It supports retrieving one list data at a time. For the multiple joined list, you still need to create custom code like MOSS 2007 (you can use sharepoint APIs or web service APIs to retrieve the data)
  • SQL Azure as report data source
  • PowerPivot Model as a report data source
  • Self-service BI – With SSRS 2008 R2, All your reports instantly become Data feeds. SSRS Report as data sources to PowerPivot for Excel analysis  (ATOM Feed),  Using reports as datasource for Analysis, IW can consume all the operational, corporate reports for their analysis. 
  • Managed Self Service BI – IT provisions data to IWs through secured, well defined, optionally pre-cached reports

Here are more info.

Hope this will help

This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s