Benefits of using Reporting Services in SharePoint integrated mode
- Version Control in SharePoint (vs. BIDS project saved in TFS). Having version control for reports is critical, especially if you allow end users to use Report Builder. Using BIDS with TFS is fine. But if you are directly using Report Builder with Report Server native mode is terrifying.
- Check-in / check-out
- Draft/publish versions
- Alerts (when someone updates reports)
- Workflows (though to be honest - I have yet to see a business reason to use workflow for .rdl)
- If you are using SharePoint to surface your reports, the integrated webparts makes sense. Though with reporting server in native mode you can still use a Report Viewer webpart via IFrame.
Same / Similar functionality
- Report Subscriptions are handled by RS
- URL: Report Server or SharePoint document library
- Permissions control either in Report Server, or in SharePoint
Problem / suggestions
- To use integrated mode you _do_ need to have SharePoint somewhere. Sometimes a company may only have a database and don't even have IIS on the database server.
- But if you use native mode, and need some sort of source control, you'll need TFS. So may be install SharePoint is more useful than TFS for a power user / BI Expert.
- A reporting service can only connect to one SharePoint - you can't join two different farms (e.g. dev sp and prod sp). This was a concern during migration to SP2010 - some reports are for intranet and some for public… can't move one or another.
- Report database cannot switch modes between native and integrated - so migrating reports is a pain in the butt - you need to export old reports, create a new report database and choose integrated mode, then add them back in. A bit painful I think.
- The UI for setting up BIDS project to export to SharePoint integrated mode is REALLY crap. I have no mercy for this crap dialog:
- TargetServerURL: http://Server/ReportServer
- TargetDataSourceFolder: /Data Sources <- OK. Deploy no problems.
- TargetServerURL: http://server
- TargetDataSourceFolder: /Documents/Data Sources <- wrong!
- TargetDataSourceFolder: http://server/documents/Data Sources/ <- correct. Need entire URL. WHO THE HECK KNOWS THIS WITHOUT THE TOOLTIP?
If you don't set up the folder properly as per example. BAM deploy fail no proper errors. Just says no permission to path or some irrelevant rubbish - sends you in circles thinking you stuffed up SharePoint…