I wanted to record an introduction to the new reporting and Business Intelligence capability within SharePoint 2013. After loading SP2013, there are a few steps to activate the backend Service Applications for BI. The SQL 2012 install media is needed for this to install SSRS Integrated Mode and PowerPivot.
However, once those are online you can load great samples like “PowerView – Hello World Picnic” to browse real data and confirm it all works correctly. Very cool stuff, enjoy!
Check out the below video to learn how to test SQL Server Reporting Services. After installing to Central Admin with the steps from http://msdn.microsoft.com/en-us/library/jj219068.aspx I wanted to see a real report to confirm successful install. A simple SharePoint list with US state postal abbreviations connects to RDL with Map Wizard and is a great way to show the full pipeline works correctly:
SSRS Service Instance (on server)
SSRS Service Application (on farm)
Authentication (C2WTS or Kerberos)
Site Feature (PowerView Integration)
Site Content Types (Report Builder Model – SMDL, Report Builder Report – RDL, Report Data Source – RSDS)
Report Builder 3.0 (web deploy click once)
RDL web rendering engine
Export to PDF web actions menu
If you find this helpful, please leave a comment and I’ll try to do more videos.
Today a new download showed up on my RSS feeds and I wanted to take a minute to compare this new MSI file against the trusty old MSI I’ve used for so long now. As you know, the SharePoint 2010 Prerequisites installer requires “rsSharePoint.msi” to be loaded before you can install SharePoint 2010. Below is the OLD link for SSRS which most people use today for cool stuff like a PowerShell script to download all Prerequisites for offline install. as well as the NEW link. The release of Service Pack 2 for SQL 2008 R2 seems to be triggering lots of new downloads so it might be worthwhile to make sure you’re SharePoint front end binaries match the backend SQL server version. If patching SQL to SP2, then it’s probably a good idea to update the web front end components and look for the “4000” version number.
It might be a good idea to download the most recent add-in for any new server installs. There appear to be updates to most all files, but “sqlserverspatial.dll” grew more than most possibly hinting at better geographic data support.
