a primer on power pivot topology and configurations
DESCRIPTION
This is a quick primer on the topologies and configurations surrounding PowerPivot.TRANSCRIPT
A Primer on PowerPivotTopology and Configurations
Denny LeePrincipal Program Manager
SQL Customer Advisory Team
Agenda
• PowerPivot Component Infrastructure• Capacity Planning• Configuration • Installation• Upload Configuration• Troubleshooting
PowerPivot for ExcelPowerPivot Component
Infrastructure
PowerPivot for ExcelThe database is IN the workbook
Excel
PowerPivot Add-InMSOLAP
AMO ADOMD.NET
VertiPaq Engine
PowerPivot for ExcelArchitecture
Excel Client
PivotTable MSOLAP
In-Proc
TCP
HTTP
VertiPaq
PowerPivot Add-In
AMO
ADOMD.NET
PowerPivot for SharePointPowerPivot Component
Infrastructure
PowerPivot for SharePointExcel Services Rendering
Data Source:Analysis Services
Excel Services
Excel Web Access
Excel Calculation Services
Excel Web Service
OLE DB Provider:
Analysis Services
TCP Protocol
Excel Services: Render a workbook connected to SSAS
PowerPivot for SharePointExcel Services Topology
WFE
Excel Web Access
App
Excel Calculation Services
Content
SQL
Excel Web Service
SharePoint Farm
OLE DB Providers
Analysis Services
SQL
Other Providers
Data Sources
PowerPivot for SharePointPowerPivot Services Components
WFE
PowerPivot Web Service
AppPowerPivot
System Service
Content
SQL
Analysis Services Engine Service
SharePoint Farm
PowerPivot System Service Notes: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, responseTimes, server health, load and unload, etc.)
PowerPivot for SharePointOLE DB for Analysis Services Driver
App
MSOLAP
TCP
HTTP
Channel
PowerPivot System Service
WFE
Other SharePoint FarmPowerPivot enabled
SharePoint Farm
WFE
Content
SQL
PowerPivot for SharePointLoad Balancing
WFE App
PowerPivot System Service
Excel Calculation Services
Content
SQL
MSOLAP
Channel
TCP
HTTP
Excel Web Service
Analysis Services Engine Service
SharePoint Farm
5
Proxy Endpoint
Excel Web Access
PowerPivot Web Service Proxy Endpoint
4
1
6
2
3
PowerPivot for SharePointRendering a workbook w/ server action
WFEExcel Web
Access
App
PowerPivot System Service
Excel Calculation Services
Content
SQL
MSOLAP
Channel
TCP
HTTP
Excel Web Service
Analysis Services Engine Service
SharePoint Farm
1 2
3
4
5
PowerPivot for SharePointGeneva Claims Token / c2wts
AppWFEExcel Web
Access
AppExcel Calculation
Services
Content
SQL
Excel Web Service
SharePoint Farm
1 2 PowerPivot System Service
Analysis Services Engine Service
34
Capacity PlanningA Preview to PowerPivot Best
Practices
Capacity Planning:Basic observations
• VertiPaq mode is an in-memory system− Any currently ‘in-use’ database must be in memory (add’em
up)− Need some buffer (~10-20%) for the auto-detection to work
effectively • To reduce impact on content database, PowerPivot
keeps a ‘cache’ of detached databases in the SSAS Backup folder
Capacity Planning:Provisioning
Metric Determination
Total # of Users • Ascertain maintenance costs for user-base
• Storage Requirements = Avg # of files x Avg Size of files x Total # of Users
Total # of Concurrent Users
Help determine number of SharePoint WFEs
Total # of PowerPivot Users
Help determine number of SharePoint Application Servers (hosting Excel Services, AS Engine, PowerPivot System Service)
# of Files; Avg/Max Size of Files
Necessary to determine storage requirements to 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
Capacity PlanningScale Out Content Database
SharePoint Farm
WFE
App Servers
Content dBs
• Excel workbooks (or any file) stored as blobs in content database
• Another option is to use Remote Blob Store to store in FILESTREAM or connected network storage (e.g. EMC Centera)
• Preliminary results note low overhead (2-3%) and able to better handle higher concurrency scenarios
TopologiesA Preview to PowerPivot Best
Practices
http://go.microsoft.com/fwlink/?LinkID=167089http://sqlcat.com/whitepapers/archive/2010/04/23/powerpivot-technical-diagram-powerpivot-client-server-architecture.aspx
SharePoint Server 2010 TopologiesMedium Server Farm Topology
SharePoint Server 2010 TopologiesPowerPivot Departmental Topology
WFE
PowerPivo
t
Excel Svcs
SQL
• Good for small setups• Not a good farm scenario • Should work fine in
Kerberos or Claims scenarios
Single Server Multiple Standalone Server
• Evenly distributes load across many servers*
• Easy to rebuild but doesn’t take into account heavier loads
• Should work in Claims and Kerberos
SharePoint Farm
SharePoint Server 2010 TopologiesEnterprise Topology (1)
SharePoint Farm
WFE
PowerPivo
t
Excel Svcs
SQLPowerPivo
t
PowerPivo
t
WFE
Excel Svcs
web app dB
Application Servers are PowerPivot Only• Scenario is good if
PowerPivot servers have the most amount of load
• Not as common because most calculations in PowerPivot are not overly complex
• May be helpful for Report Builder and Performance Point scenarios
• Should work in Claims and Kerberos scenarios
SharePoint Server 2010 TopologiesEnterprise Topology (2)
SharePoint Farm
WFE
SQL
PowerPivo
t
WFE
web app dB
Application Servers are PowerPivot and Excel Services• Scenario is good if
WFE servers have the most amount of load
• May be a good idea due to high amount of chatter between Excel Services and PowerPivot
• Should work in Claims and Kerberos scenarios
Excel Svcs
PowerPivo
t
Excel Svcs
PowerPivo
t
Excel Svcs
SharePoint Server TopologyMulti-hop scenario?
SharePoint Farm
SQL
WFE
web app dB
Multi-Hop• By definition, going from
the client to Excel Services to PowerPivot server is multi-hop
But• Excel Services and
PowerPivot Services are service applications
• PowerPivot System Service recreates the identity token
BackgroundWith SharePoint 2010, we have Claims token as part of Geneva framework
Excel Svcs
PP Servi
ce
Client
ASEngin
e
SharePoint Server TopologyClaims Data Source Scenario
SharePoint Farm
SQL
WFE
web app dB
• PowerPivot System Service Login
• AS Engine Service Impersonates SSS credentials
• Connects to Data Source 1 via impersonation
Excel Svcs
PP Servi
ce
Client
ASEngin
e
Data Sourc
e 1
SharePoint Server TopologyKerberos Data Source Scenario
SharePoint Farm
SQL
WFE
web app dB
• Still need Kerberos in scenarios like above.
• Constrained Delegation by machine (less secure) or user account (more secure)
• This is defined by settings on Data Source 2
Excel Svcs
PP Servi
ce
Client
ASEngin
e
Data Sourc
e 1
Data Sourc
e 2
Linked To
Kerberos
InstallationA Preview of PowerPivot Best
Practices
Installation Best Practices
• Read the manuals!!!• There are a lot of steps and a lot components
integrated together:− PowerPivot System Service, AS Engine, SharePoint, Excel
Services, Reporting Services, Excel Client, Office Workspace, IIS, Windows, etc.)
• Examples:− To change password for SharePoint Farm takes seven
separate steps in the farm, services, and IIS.− Multiple steps to handle larger file sizes
Installation Best PracticesGotchas!• “New Farm” vs. “Existing Farm”• Require Domain Accounts• Upgrade SharePoint 2007 to SharePoint 2010 is very
complex• Cannot upgrade from Gemini Server
− CTP2 -> CTP3: Cannot do− CTP3 -> RTM: ??
Upload ConfigurationA Preview of PowerPivot Best
Practices
Upload ConfigurationOverview• SharePoint is optimized for download, hence our
concerns for PowerPivot scenarios were for upload• Important because IT (SharePoint) Administrators
are now dealing with larger files− Default SharePoint Scenarios
− Max Size: 50Mb; Average Size: 20Mb− PowerPivot SharePoint Scenarios
− Max Size: 2000Mb (configure Excel Services and SharePoint); Average Size: ~50Mb
− Install instructions provide how to configure this
• New: Office Sync Center which can asynchronously upload files from Excel to SharePoint
Upload ConfigurationSharePoint LargeChunkFileSize
LargeChunkFileSize parameter little to no effect on upload performance
Upload ConfigurationEffect of Bandwidth (100Mbps vs. 1Gbps)
Upload ConfigurationEffect of Bandwidth (Various)
Corp (100) T1 (1.54) Comcast (1.00) OC3 (155.52)0:00:00
0:28:48
0:57:36
1:26:24
1:55:12
2:24:00
2:52:48
3:21:36
3:50:24
4:19:12
0:19:56
2:29:27
3:41:03
0:53:16
Average Upload Duration for 1.3GB to SharePoint
Bandwidth Category
Upload ConfigurationSharePoint Upload vs. File Copy
25 43 75 128 223 388 536 822 12400:00:00
0:01:26
0:02:52
0:04:19
0:05:45
0:07:12
0:08:38
0:00:00 0:00:01 0:00:02 0:00:03 0:00:06 0:00:11 0:00:150:00:37
0:00:59
0:00:09 0:00:15 0:00:270:00:42
0:01:11
0:02:11
0:02:57
0:04:32
0:06:55
WebDav vs. FileCopy Speed by File Size (1Gb)
FileCopyWebDav
File Size (MB)
TroubleshootingA Preview of PowerPivot Best
Practices
TroubleshootingReading ULS Logs
%commonprogramfiles%\Microsoft Shared\Web Server Extensions\14\LOGS\
TroubleshootingSQL Profiler
Q&A
© 2009 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.