Configuring SharePoint for Business Intelligence

Editor's Notes

• #6: Here’s a little demonstration of what you can do when you have it all working together…The GSAF is a loose collection of all reported shark incidents
• #7: Org BI has been with us forever – Decision Support Systems – Reliable and curated, but unresponsivePersonal BI evolved to plug the performance gap – problem is that it’s unreliable and out of controlAllow users to share, with oversight in a team scenario – that’s what SharePoint provides. A platform for reliable BI collaboration
• #8: The products stack up much as expected, with SQL Server SKUs filling the Enterprise spaceOffice apps as expected cover much of the Personal BI space – with add-ins from the SQL teamThe team area is a mixture, with products from both teamsIt’s worth noting that the second most requested feature of any 3rd party BI application is export to Excel. Using SharePoint, Excel can actually be a client, meaning it can stop being a part of the problem and become a part of the solution.
• #9: Another way to look at the tools – through their uses
• #11: Big change is that xVelocity is included, as have PowerPivot and PowerViewParalleling that on the server, what was once simply PowerPivot for SharePoint has been segmented into its two constituent parts. It was always Analysis Services + automation, but it was tightly coupled. Now it can be scaled separately, and Excel Services handles the load balancingA number of other new features are available that may affect architecture, including per-user authentication
• #12: Covering 3 Major AreasExcel ServicesReporting ServicesPerformancePoint
• #13: Excel the client enables the personal BI.Office Pro Plus means NOT Home and Student, or RT – no model for surface… In 2013 xVelocity is built in, and PowerPivot and PowerView are included and must be enabled (show)To share workbooks, Excel services is necessary. Interaction with the data model requires Analysis Services SharePoint modeTo refresh automatically and use the Gallery, you need PowerPivot for SharePoint
• #14: Although PowerPivot and Power View are included, they are disabled by default, and need to be enabled if you want to work with them. This is done easily enough – (Demo in Excel). Also, if you click the Power View button, it’ll offer to do it for you. In addition, the xVelocity engine isn’t used by default, it must be activated on a workbook by workbook basis. There are ample opportunities to do this – when importing data, when inserting imported data into the workbook, or when working with the data. Finally, if PowerPivot is enabled, using it will also create the model.
• #15: 4 client versions, 3 server versions. SQL Server 2012 SP1 brings new features to the table – required for the new models
• #16: What works with what? Essentially, you’re looking at good downward compatibilityOf note – Excel 2013 models won’t work with pre 2013 SharePoint farms. Just sayin’Upgrade your farm before your Office apps
• #17: SSRS is comparatively generous – doesn’t even need a SharePoint licenseSharePoint mode does need at least a standard license (there’s an Express…)The really cool features need BI or EnterprisePowerView needs Tabular models
• #18: PerformancePoint is an aggregatorRequires SP EnterpriseAS needs to be available for analytics charts or grids (either mode)
• #19: Some pieces are built by the Office team, some by the SQL Server teamCan lead to confusion – consider ta common misunderstanding
• #20: This is a very common small farm architecture. All the SQL bits on one server, all the SharePoint bits on anotherReporting Services and PowerPivot for SharePoint are on the SQL server mediaBoth require Farm joined servers to operate
• #21: Far too often, this is what results. SharePoint gets laid down on the SQL boxSQL performance is impactedManagement headaches increase
• #22: Correct approach is to put the SQL bits on the SharePoint server not the other way around
• #23: Let’s walk through the setup of the 3 major groups, starting with Analysis Services SharePoint mode/PowerPivot
• #24: These screens look the same for installation on Standalone or on SharePoint“SQL Server PowerPivot for SharePoint” is ConfusingNeed BI or Enterprise license to see this option
• #25: - This is the only place where we see the terminology “Analysis Services”
• #26: Must install into a named instanceLeaving it as PowerPivot not required, but recommended
• #27: Must use a domain account – shouldn’t be a managed one
• #28: - Accounts used to connect through BISM MUST be AdministratorsFarm account should be administratorNext up – Go to Excel Services Application settings and show the data model settings
• #29: - At this point, we can register the engine with Excel Services, and we’re good
• #31: From here only applies to installation on a SharePoint ServerRequired for scheduled refreshes, PowerPivot galleryDo NOT need to have the Analysis Services instance on the same server (but you can (classic mode))
• #32: Already configured in this farm, so we’ll use screenshots. Starting with 2012, the configuration tool was added. When you run it, you get the option of configuring, repairing or removing PowerPivot for SharePointIf you want to remove it – use this tool
• #33: The tool analyzes the system to determine what is necessary for configurationWhere input is needed, you see an alert
• #34: I recommend changing the name of the application and the databaseDefault PowerPivot is a bad name, and GUIDs are evil
• #35: - The tool will deploy assets to a single site collection. If you have multiple, this must be done manually
• #36: When Ready, use the validate button, and all indicators should turn greenThere are a couple of post configuration steps that need to be doneChange the Excel Services default sizeAdd the Central Administration address into trusted pathsChange the prompting optionsGrant spServices correct permissions in the Administration databaseCheck the data model settings
• #38: Setting Up:Service ApplicationSubscriptions and AlertsReport Library – Report Builder/Data Tools for ContentBISM Connection – Power View Report
• #39: We’re not doing PowerPivot, so we select SQL Server feature installation.
• #40: - RS – SharePoint is the Service Application- RS Add-in for SharePoint is the old fashioned add –in MUST be deployed on all front end servers!
• #48: PerformancePoint is straightforwardCan be done by the “white wizard”
• #55: As with any SharePoint service application, BI features can be scaled out nowA few differencesWorth walking through a growth scenario
• #56: Start with an all in one SharePoint farm (NOT a standalone!)
• #57: Let’s add or BI services to our SharePoint box. Simple enough
• #58: Now lets move the server that the users interact with (the FE server) onto its own box. We can also separate out the model processing onto a standalone (non farm joined) server. This way, services execution doesn’t impact user requests.
• #59: Another approach is to segment by functionNot strictly role basedLong running processes separated from user interacting processes
• #60: - Obviously all of these services can themselves be scaled out and load balanced
• #61: For SSRSService app needs to be installed on “application server” roles – Responsible for processing and rendering the reportAdd in must be installed on FE server – unlike the past where it was automatic. Connects to service appFor xVelocityAdd “PowerPivot for SharePoint” to standalone serversAdd “PowerPivot for SharePoint” add in to at least one “application server” roleBoth can be on one – will impact SP performance
• #62: A non-comprehensive collection of things to be aware or “notes from the field”
• #63: Explain Double hop problem Kerberos constrained delegation allows token passing, but hard to set upReporting Services has supported this for a long time via SetUser() – nobody understood itBISM implicitly supports EFFECTIVEUSERNAMEPerformancePoint and Excel Services now support EFFECTIVEUSERNAME against multidimensional sources
• #64: Quick demo using SSRS on how this works
• #65: - Connection account needs very elevated permissions to use (dbOwner or SysAdmin) Keep in mind the the service account for the services in question need Admin access to the Analysis Services server (makes a connection)EXCEL Services and PerformancePoint for AS, SSRS for SQL (except PowerView, which is BISM)
• #66: Real value of SP as a platform is its integration capability. Whole > sum of partsDashboarding is obvious – pull together assets from all of the different tools using the web part framework.To consider – leverage other SharePoint assets – like the filter parts, in particular the current user filter. To use this filter effectively, your user profile subsystem must be healthy. Many people are unaware of it, or its extensible powerOld import system available in SP2013
• #67: Integration in Action – Using a profile field to drive an SSRS parameter
• #68: More integration – turning things around. How to Report on SharePoint DataSP data design makes it inefficient. Best to extract into a data warehouse like other transactional systemsImprove performance and simplify maintenanceWorkflowHistoryList is a prime exampleBlog entry of how to clean out
• #70: Everyone has a red bar. Need to fix thisProblem is spurious rules – need to repair real problems – disable spurious rules