Transforming Data Streams with Kafka Connect: An Introduction to Single Messa...
Power pivot planning_and_deployment_whitepaper
1.
2. Registry settings and manifest files Enable Excel 2010 to load PowerPivot at run time. The registry settings under HKEY_CURRENT_USERoftwareicrosoftfficexcelddins point to the deployment and application manifests, which are Extensible Markup Language (XML) files that describe how to load the add-in assembly.
3. VertiPaq engine Processes PivotTable and PivotChart queries and DAX expressions. The VertiPaq engine leverages the richness of Analysis Services object models internally, but without imposing dimensional modeling concepts on users.
4. VertiPaq database Stores the PowerPivot data. The VertiPaq module maintains its database in a custom XML part within the Excel workbook. Note that you can locate the VertiPaq database in an Excel file by renaming the workbook using the .zip file extension, opening the .zip file in Windows® Explorer, and then navigating to the xlustomData folder. For technical details, refer to the blog post “For Excel PowerPivot, the Database is IN the Workbook” at http://go.microsoft.com/fwlink/?LinkId=181771.
5. Data cache Stores temporary files during save operations in the %TEMP% directory. With the exception of this temporary data cache, PowerPivot maintains no data outside the Excel workbook. For details, refer to the blog post “Understanding why an Excel PowerPivot Workbook is so Large” at http://go.microsoft.com/fwlink/?LinkId=181773.
6. Microsoft OLE DB for Online Analytical Processing (OLAP) Exposes a set of COM objects and interfaces to access multidimensional data stores. The OLE DB for OLAP provider can connect to SQL Server Analysis Services as well as PowerPivot workbooks on the local computer or published in a SharePoint farm.
7.
8.
9. Data Cache Maintains workbooks in memory and on disk in the %PROGRAMFILES%icrosoft SQL ServerSAS10_50.PowerpivotLAPackup folder to increase system performance by eliminating roundtrips to the SharePoint content database.
10. Excel Calculation Services Loads PowerPivot workbooks in much the same way as other Excel workbooks, calls user-defined functions if necessary, and refreshes external data as needed, such as when a user interacts with PivotTables or PivotCharts via slicers. The connection information for PowerPivot data points to the PowerPivot OLE DB provider, which enables Excel Calculation Services to request the data from the PowerPivot system service. The DataSource property for VertiPaq databases is listed as $EMBEDDED$.
11. Excel Web Access Renders workbooks on a Web page and allows the user to interact with those workbooks and explore them in Microsoft Internet Explorer®. Excel Web Access does not require Excel on the client computer. The Excel Web Access Web part renders the workbook using Excel Calculation Services.
12. Excel Web Services Provides programmatic access to workbooks. Business applications can calculate, set, and extract values from workbooks, refresh external data connections, and create application-specific user interfaces around shared workbooks.
13. PowerPivot Application Database Stores configuration settings, connection information, server status, and schedule information for data refresh operations.
14. PowerPivot Gallery Implements custom content types and Microsoft Silverlight™-enabled application pages for document libraries to visualize shared workbooks and Reporting Services applications interactively.
16. OLE DB Provider Enables Excel Calculation Services and other processes, such as Reporting Services and PerformancePoint Services, to locate and establish connections to a PowerPivot system service in the local farm or a PowerPivot Web service in a remote farm. The PowerPivot transport and connection logic is directly integrated into the Analysis Services OLE DB provider of SQL Server 2008 R2, which also provides connectivity to SQL Server Analysis Services (SSAS). The OLE DB provider uses the IsHosted flag to distinguish between SSAS and PowerPivot clients and relies on Windows Communication Foundation (WCF) to communicate with a PowerPivot system service in the local farm or Hypertext Transfer Protocol (HTTP) to communicate with PowerPivot Web services in remote farms.
17. PowerPivot System Service Uses Microsoft ADOMD.NET to communicate with an Analysis Services instance. The PowerPivot system service also manages the application database, monitors server health, coordinates client requests for load balancing, collects usage data, and performs automatic data refreshing for PowerPivot workbooks.
18. PowerPivot Web Service Exposes shared PowerPivot workbooks via XML for Analysis (XML/A) as data sources to external applications, such as Excel or Microsoft Report Builder 3.0. Support of XML/A enables any client application that uses Multidimensional Expressions (MDX) and the Analysis Services OLE DB provider to query PowerPivot data in workbook applications hosted in a SharePoint farm.
19. Service Applications Provide backend services for Web applications. SharePoint 2010 no longer uses Shared Services Providers (SSP). Instead, SharePoint 2010 uses an Internet Information Services (IIS) Web site called SharePoint Web Services, which hosts all service applications in one or multiple application pools for security and process isolation. Default and custom service application groups associate service applications with Web applications.
20. Web Applications Provide IIS sites and application pools, security identities, and isolation for front-end processes on a SharePoint server. A single Web application can host multiple site collections and each site collection can have the PowerPivot feature activated or deactivated individually.
21.
22. Data is not loaded but it is cached. The PowerPivot service application checks its internal list of cached PowerPivot datasets that are already on the file system. If the same PowerPivot dataset is cached on multiple servers, the PowerPivot service application will check server health and build a list of servers that have sufficient resources to accept the request. From that list, a server is picked at random.
23.
24. Streamlined security and compliance management SharePoint provides the infrastructure for access-based security, authentication, and compliance policies. There is no need to log on to multiple applications. SharePoint identifies each user based on the Windows account, and shows only those resources the user can access.
25. Resourceful use of database storage SharePoint stores user data, such as PowerPivot workbooks, in content databases. Factors that influence the database storage requirements include the maximum upload size, which determines the maximum item size, as well as versioning and recycle policies. PowerPivot workbooks typically contain more data than standard Excel files (up to a maximum of 2 GB), and thus typically require more storage capacity than other service applications. In a centralized environment, a high-end storage area network (SAN) solution can provide the required capacity with higher availability levels than direct attached storage (DAS) solutions in departmental farm environments.
26. Increased availability, performance, and scalability For SharePoint relational database uses in SAN-based environments, SQL Server supports the deployment of failover clusters to achieve a very high resilience against single-point failures. It is also possible to deploy multiple front-end and application servers for load-balancing and failover redundancy. Having multiple PowerPivot servers provides for high availability, better performance, and scale-out capabilities. These advanced system configurations are usually cost-prohibitive in decentralized environments with small SharePoint farms.
27. Efficient enterprise search capabilities SharePoint Server 2010 includes an Enterprise Search Center to locate business documents and PowerPivot workbooks quickly in order to accelerate decision-making based on the latest information. Centralized environments require less administrative overhead to implement and maintain enterprise search.
28. Reduced operations and development costs The centralized BI collaboration environment reduces the need to deploy, maintain, and support isolated BI environments. It also helps to coordinate development processes; share workflows and BI effectively across organizational boundaries; eliminate duplicated efforts; and achieve a high level of consistency across all BI solutions.
29.
30. Onboarding After testing and stabilizing the deployment, the IT team transitions the initially selected departments to the collaboration environment while monitoring system reliability, PowerPivot performance, and database storage consumption. If necessary, the IT team also provisions Web applications and site collections for the departments. The IT team can delegate administrative permissions at the site-collection level so that each individual department can subsequently provision its own site hierarchies and define user permissions.
31. Stabilizing Following the successful transition, the IT department can start the user acceptance phase. During this process, power users must confirm that the PowerPivot environment works as expected. The IT team keeps track of any issues and coordinates the required solution steps, such as adding further application servers and storage resources to ensure scalability, availability, performance, and quality of service.
32. Onboarding Whenever a new department agrees to onboard to the managed BI collaboration environment, the overall deployment cycle begins again with an initial assessment of requirements, proactive deployment of additional resources, and the final transition of the selected department.
35. Determine the security roles specifying who can access the uploaded workbooks and who can modify the workbooks.
36. Specify that a workbook can be rendered only online and that the file can’t be downloaded (view-only permission).
37. Manage data refresh settings, including the refresh schedule, user credentials for the update process, and the portions of the dataset that should be updated.
38.
39. Visit the PowerPivot site and download either the x86 (32-bit) or the x64 (64-bit) version of PowerPivot_for_Excel.msi.
48. Create a PowerPivot Service Application Web applications require a PowerPivot service application to access the PowerPivot servers in the farm, which provides an endpoint to the PowerPivot system service. It is possible to create multiple PowerPivot service applications and add the corresponding service application connections to different service connection groups. However, make sure that the default service connection group includes a PowerPivot service application. Otherwise, PowerPivot Management Dashboard will not work properly.
49. Activate Excel Calculation Services and Secure Store Service By default, SharePoint 2010 does not enable Excel Services, but PowerPivot for SharePoint requires this feature to support PowerPivot data access in the farm. PowerPivot for SharePoint also requires the Secure Store Service feature to store credentials and the unattended execution account for data refresh. By enabling Secure Store, workbook authors and document owners can access a broader range of data source connection options when scheduling data refresh for their published workbooks.
50. Configure Automatic Data Refresh Workbook users can refresh data on demand in PowerPivot for Excel, but PowerPivot for SharePoint also supports data refresh as a scheduled operation to re-import data from external sources; this runs as an Analysis Services process on an application server in the farm.
51. Increase the Maximum Upload Size Because PowerPivot workbooks can be large, Microsoft recommends increasing the maximum upload size to 2 GB for Web applications with access to PowerPivot service applications.
52. Enable Usage Data Collection PowerPivot for SharePoint uses the SharePoint usage data collection infrastructure to gather information about PowerPivot usage throughout the farm. Although usage data is always part of a SharePoint installation, it must be enabled before it can be used.
53.
54. Involve the relevant contributors and stakeholders Implementing a PowerPivot BI solution requires participation from application developers, information workers, executive and other decision makers, and IT professionals. Although workers can create individual BI applications, the IT organization must design and deploy the environment, provision data sources, and assign permissions to provide the underlying platform. Gathering those requirements and obtaining input from leadership is crucial to project success.
55. Engage power users and business users Managed, self-service BI is about providing business insights to all employees. It is therefore a good idea to include power users and business users even in the earliest stages. Heavy involvement and actual face time is critical to successful PowerPivot engagement.
56. Focus resource time on key competencies With key decisions that need to be made about topology, server sizing, logical design, and rollout phases, it is a best practice to delegate responsibilities according to expertise. By defining roles and responsibilities from the onset, it is straightforward to identify gaps in resources and tasks, and to ensure that people focus on completing tasks for which they are qualified.
57. Get executive buy-in Making a change to the existing BI environment or driving adoption of a new one is easier if the strategic direction of the organization recognizes the importance of self-service BI. Project success for BI often depends not as much on technical completion as on demonstrating the ease of use and business benefits a new platform provides.
58. Onboard gradually and stabilize Because establishing a managed BI collaboration environment is a strategic effort that has the potential to influence all areas of an organization, it is important to drive adoption in stages. Onboarding in phases has the advantage of enabling users to become familiar over time and providing IT enough time to respond to issues and fine-tune configuration settings according to individual department needs.
59. Use clear documentation and training As in any project that implements new systems and processes, it is vital for users to have clear steps for onboarding and usage. Consider establishing a knowledge base for common questions and include training videos and details about common data sources that can be used for many types of BI applications.
60. Right-size storage and connectivity The client and server components of PowerPivot provide fast processing capabilities with features such as the in-memory engine, but that speed and reliability depend on the underlying components performing as expected. The two most common performance issues relate to disk size or speed on the back-end storage subsystem or to connectivity when transferring large amounts of data. It is important to plan for appropriately sized servers and bandwidth for the organization’s needs.
61.
62. Are you rating it low due to poor examples, fuzzy screen shots, or unclear writing?This feedback will help us improve the quality of white papers we release. <br />Send feedback.<br />