A primer on power pivot topology and configurations


Published on

This is a quick primer on the topologies and configurations surrounding PowerPivot.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 2nd bullet no limit on the size of the on-disk space takenPossible / Make it discussionClientProducer (Windows 7, dual core, 4GB RAM)Allows Windows Desktop Experience for UploadMore memory and CPU to process dataConsumer: Regular PC (browser-based)Server (64GB RAM, 64-bit, multi-core)SharePoint 2010 requires 64-bitAllows for multiple configurations (more later)
  • Introduce concept of Claims authentication here*Provided NLB in front of servers
  • Another option is to have separate servers for all components but most likely not optimal use of resources
  • FYI – the steps are: Change the service account passwords from the services.msc (SQL Server, Analysis Services, Reporting Services, etc.) The lab account pwd has changed so I was not able to connect to the SharePoint Central Admin.  Therefore, followed steps 1 – 5 at http://support.microsoft.com/kb/934838 Now that I can connect to SharePoint Central Admin, needed to configure the Managed accounts 1.            In the Central Admin – Security – Configure Managed Accounts2.            Edit the account you want to change the password for.3.            In section for Credential Management, select “Change password now” and  select “Use Existing password” and type in the new password. All services are up and running but the application pools need to be reset within IIS o IIS Manager -> Application pools, right-click on the “SharePoint Web Services System” app pool -> advanced settings -> set account. Then start the pool. If you are on a newer build the app pool name is a guid.   Ensure to change all of the app pools running under the changed account.
  • Exponential difference for different bandwidth for WebDav upload
  • Using Cobalt protocol (TBD), see how much slower it is by having so much slower bandwidth
  • Comparison of FileCopy vs. WebDAV – for remote systems, perhaps want to filecopy it to a local box and then upload if speed is concern. Otherwise, use Office Sync Manager to do the upload async – though there can be issues with this (when the file was uploaded, etc.)
  • Thanks to John Sirmon for these screenshots
  • Thanks to John Sirmon for these screenshots
  • A primer on power pivot topology and configurations

    1. 1. ••••••
    2. 2. PowerPivot for ExcelThe database is IN the workbook Excel PowerPivot Add-In MSOLAP AMO ADOMD.NET VertiPaq Engine
    3. 3. PowerPivot for ExcelArchitecture Excel Client PowerPivot AMO Add-In ADOMD.NET PivotTable MSOLAP VertiPaq TCP HTTP In-Proc
    4. 4. PowerPivot for SharePointExcel Services Rendering Excel Services: Render a workbook connected to SSAS Excel Services OLE DB Provider: Data Source: Analysis Services Excel Web Analysis Access Services Excel Calculation Services TCP Protocol Excel Web Service
    5. 5. PowerPivot for SharePointExcel Services Topology SharePoint Farm Content WFE App SQL Excel Web Access Excel Calculation Services Excel Web Service OLE DB Providers Data Sources Analysis Services SQL Other Providers
    6. 6. PowerPivot for SharePointPowerPivot Services Components SharePoint Farm WFE App PowerPivot PowerPivot Web Service System Service Analysis Services Engine Service Content PowerPivot System Service Notes: SQL Controls the instance map that attach/detach dBs, data refresh jobs (schedule, history), and pushes usage events to the SharePoint usage database and PowerPivot database (including connections, response Times, server health, load and unload, etc.)
    7. 7. PowerPivot for SharePointOLE DB for Analysis Services Driver SharePoint Farm App MSOLAP TCP WFE HTTP WFE Channel Other SharePoint Farm PowerPivot enabled PowerPivot System Service Content SQL
    8. 8. PowerPivot for SharePointLoad Balancing SharePoint Farm WFE App Excel Web Excel Calculation MSOLAP Access 1 Services Excel Web TCP Service 2 HTTP PowerPivot Proxy 3 Web Service Endpoint 6 Proxy Endpoint Channel PowerPivot 4 System Service Analysis Services 5 Engine Service Content SQL
    9. 9. PowerPivot for SharePointRendering a workbook w/ server action SharePoint Farm WFE App Excel Web Excel Calculation 3 MSOLAP Access Services 1 Excel Web 2 TCP Service HTTP 4 PowerPivot Channel System Service 5 Analysis Services Engine Service Content SQL
    10. 10. PowerPivot for SharePointGeneva Claims Token / c2wts SharePoint Farm WFE App App Excel Web Excel Calculation PowerPivot 1 2 Services 3 Access System Service Excel Web 4 Service Analysis Services Engine Service Content SQL
    11. 11. • in memor − −•
    12. 12. Metric DeterminationTotal # of Users • Ascertain maintenance costs for user-base • Storage Requirements = Avg # of files x Avg Size of files x Total # of UsersTotal # of Concurrent Users Help determine number of SharePoint WFEsTotal # of PowerPivot Users Help determine number of SharePoint Application Servers (hosting Excel Services, AS Engine, PowerPivot System Service)# of Files; Avg/Max Size of Necessary to determine storage requirements toFiles host SharePoint data (PowerPivot and non- PowerPivot).Data Refresh Options • Security and driver issues – users will have access to data sources that PowerPivot may not have • Frequency and # of files dictate how much resources used to process/open/store these files
    13. 13. SharePoint Farm • Excel workbooks (or any file) stored as blobs in content database WFE • Another option is to use Remote Blob Store to store in FILESTREAM or connected network storage (e.g. EMC Centera) • Preliminary results note low App Servers overhead (2-3%) and able to Content dBs better handle higher concurrency scenarios
    14. 14. http://go.microsoft.com/fwlink/?LinkID=167089http://sqlcat.com/whitepapers/archive/2010/04/23/powerpivot-technical-diagram-powerpivot-client-server-architecture.aspx
    15. 15. Single Server Multiple Standalone Server SharePoint Farm Power Pivot Excel WFE Svcs SQL• Good for small setups • Evenly distributes load across• Not a good farm scenario many servers*• Should work fine in Kerberos • Easy to rebuild but doesn’t take or Claims scenarios into account heavier loads • Should work in Claims and Kerberos
    16. 16. SharePoint Farm Application Servers Power Pivot are PowerPivot Only WFE • Scenario is good if PowerPivot servers have Excel Svcs the most amount of load Power • Not as common because SQL Pivot most calculations in WFE PowerPivot are not overly complex Excel • May be helpful for Report Svcs Builder and Performance Power Pivot Point scenarios • Should work in Claims and Kerberos scenariosweb app dB
    17. 17. SharePoint Farm Application Power Pivot Servers are Excel Svcs PowerPivot and WFE Excel Services • Scenario is good if Power Pivot SQL WFE servers have the Excel Svcs most amount of load • May be a good idea WFE due to high amount of Excel chatter between Excel Svcs Power Services and Pivot PowerPivot • Should work in Claimsweb app dB and Kerberos scenarios
    18. 18. SharePoint Farm Multi-Hop Excel • By definition, going from the Svcs client to Excel Services to PowerPivot server is multi-hop But WFE • Excel Services and PP Servic PowerPivot Services are e service applications • PowerPivot System Service recreates the identity tokenClient AS SQL Engin e Background With SharePoint 2010, we have Claims token as part of Geneva web app dB framework
    19. 19. SharePoint Farm Excel Svcs PP Servic e AS Data Engin Source WFE e 1 • PowerPivot System Service LoginClient SQL • AS Engine Service Impersonates SSS credentials • Connects to Data Source 1 via impersonation web app dB
    20. 20. SharePoint Farm Excel Kerberos Svcs PP Servic Linked To e AS Data Data Engin Source Source WFE e 1 2 • Still need Kerberos in scenarios like above.Client SQL • Constrained Delegation by machine (less secure) or user account (more secure) • This is defined by settings on web app dB Data Source 2
    21. 21. •• −• − −
    22. 22. •••• − −
    23. 23. •• − − − − −•
    24. 24. LargeChunkFileSize parameter little to no effect onupload performance
    25. 25. Average Upload Duration for 1.3GB to SharePoint4:19:123:50:24 3:41:033:21:362:52:48 2:29:272:24:001:55:121:26:24 0:53:160:57:360:28:48 0:19:560:00:00 Corp (100) T1 (1.54) Comcast (1.00) OC3 (155.52) Bandwidth Category
    26. 26. 0:08:38 WebDav vs. FileCopy Speed by File Size (1Gb)0:07:12 0:06:550:05:46 0:04:320:04:19 FileCopy 0:02:57 WebDav0:02:53 0:02:120:01:26 0:01:11 0:00:59 0:00:43 0:00:37 0:00:28 0:00:16 0:00:09 0:00:01 0:00:07 0:00:12 0:00:16 0:00:01 0:00:02 0:00:040:00:00 25 43 75 128 223 388 536 822 1240 File Size (MB)
    27. 27. %commonprogramfiles%Microsoft SharedWeb Server Extensions14LOGS
    28. 28. © 2009 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.