Welcome to MSDN Blogs Sign in | Join | Help

Microsoft Excel

The team blog for Microsoft Excel and Excel Services.
Introducing PowerPivot

Today we have a guest author from the SQL Server Analysis Services team, Ashvini Sharma, to tell us about the PowerPivot (née Gemini) feature that you may have heard about recently.

PowerPivot is the recently announced name of technologies this blog previously referred to by its codename, Gemini. This article describes why there is a need for such a tool, and briefly what PowerPivot provides. More information is available on the PowerPivot blog.

The Need for PowerPivot

PivotTables continue to be indispensible for allowing users to analyze their data flexibly and interactively. If you’re a subscriber of this blog, you’ve already read some of the recent articles on investments the Excel team continues to make around PivotTables for Excel 2010.

However, using a PivotTable that connects to an OLAP data source of course requires such a data source to exist. While a corporation may have many OLAP data sources where a single version of the truth and a unified model for looking at the business is necessary, this is not always the requirement.

For personal or workgroup-oriented solutions, our customers tell us there’re shortcomings in technology available: 

  1. Requires advanced technical knowledge: Creating OLAP cubes is a non-trivial effort which requires highly technical understanding of concepts such as dimensions, measures, MDX, etc. As such, IT staff is frequently called upon to create such models on behalf of business users.
  2. Incurs higher cost to solution: Since IT groups have limited bandwidth, only a few of an organization’s analysis projects get the necessary attention and resources. In order to increase efficiency, IT may also attempt to consolidate similar solutions, which incur higher coordination cost and increased time to delivery.
  3. Produces solutions that are hard to customize: Business users frequently ask for data sets or analysis paths that they could not have predicted earlier. This is typical of ad hoc analysis that PivotTables support – an answer frequently leads to the next question and it is very hard to predict all possible questions, and time consuming to bake them in the model a priori. In addition, some data, may be so specific to a business problem that one user of the model may have it on their desktop, and it is not appropriate to share it across all users of a cube.
  4. Increases cost of ownership and friction: Some business teams hire technical consultants or volunteer one of their own to take on this “burden”. Unfortunately, this responsibility goes beyond learning new technology into also developing skills and devoting time for managing and maintaining any delivered solutions. In addition, IT stays unaware of such underground applications and get rightly concerned about business decisions being made on solutions not supported by them.

Lets take a step back to make a few key observations:

  • A significant gap exists between an organization’s need for deriving insights from their data and the organization’s capacity to satisfy that need.
  • IT and business user resources are being stretched beyond their natural competencies: IT has to become more familiar with business users’ domain, and business users need to become more technical so that they can “speak” IT.
  • In our view, what’s missing is simply technology that allows business users to help themselves while providing visibility to IT, a scenario we call “Managed Self Service Business Intelligence”.

PowerPivot

The PowerPivot functionality is delivered by SQL Server’s Analysis Services team in collaboration with the Excel team and is based on our experience delivering the Microsoft Business Intelligence platform over the last decade.

There’re two components of PowerPivot: PowerPivot for Excel 2010 and PowerPivot for SharePoint 2010.

Designed for business users, PowerPivot for Excel 2010 is a data analysis tool that delivers unmatched computational power directly within the application users already know and love — Excel. Leveraging familiar Excel features, users can transform enormous quantities of data from virtually any source with incredible speed into meaningful information to get the answers they need in seconds. PowerPivot for Excel consists of the following components:

  • The Excel 2010 addin that delivers the seamless PowerPivot user experience integrated within Excel.
  • The VertiPaq engine that compresses and manages millions of rows of data in memory with blazing fast performance.

PowerPivot for SharePoint 2010 enables end users to effortlessly and securely share their PowerPivot applications with others and work seamlessly in the browser using Excel Services. PowerPivot for SharePoint also helps IT improve their operational efficiencies by tracking PowerPivot usage patterns over time, discovering mission-critical applications, and improving system performance by adding resources. PowerPivot for SharePoint consists of the following components:

  • PowerPivot Gallery – a Silverlight based gallery where users can share PowerPivot applications with others and visualize and interact with applications produced by others using Excel Services and Reporting Services.
  • PowerPivot Management Dashboard – a dashboard that enables IT to monitor and manage the PowerPivot for SharePoint environment.
  • PowerPivot Web Service – the “front-end” service that exposes PowerPivot data via XML/A to external applications such as Report Builder.
  • PowerPivot System Service – the “back-end” service that manages the PowerPivot application database, load balancing, usage data collection, automatic data refresh, etc.
  • Analysis Services – the Analysis Services server running the VertiPaq in-memory engine and integrated with SharePoint to load and manage the data within PowerPivot workbooks.

We’ll drill into these features in the next few blogs. Stay tuned!

Posted: Thursday, October 22, 2009 8:27 PM by Joseph Chirilov

Comments

Colin Banfield said:

Ash, I'd like to congratulate the team on a job well done. It appears that I might be the one buying the beer when we meet!

A couple of observations:

1)On the issue of solving the problem of cubes being unable to anticipate all possible questions a priori, I don't see PowerPivot (or any other product for that matter) solving the problem completely. The only thing that the business user can do is work with the dimensions and measures in the data warehouse (or data mart). This means that the user is limited to creating aggregations and calculated measures based on these existing dimensions and measures - which might be sufficient in most cases. The point is that if an unanticipated dimension or measure isn't in the data warehouse, then it's back to IT to address the issue.

2) I've noticed that most of the interest for PowerPivot thus far (discussions on Connect) and virtually all of the independent blogs postings are from SSAS folks - even though PowerPivot isn't this group's primary target. It appears as though the SAAS experts have seen a level of value in PowerPivot beyond what Microsoft might have anticipated. I can see where v2 of PowerPivot could be headed.

# October 27, 2009 7:22 AM

rick.lister said:

we seem to forget that multi dims are just symbolic representations of entities whether that is excel or access, or whtvr.  It will always be how you describe those entities (and the planned software apps COTS ability to independantly address these description needs [and of course the manipulative needs] that will determine complexity and outcome) provided you trust in complexities to be able to deliver.

You can't get intelligently detailed answers if you don't brush up against the complexities.  where the wild things are :)

# October 29, 2009 10:41 AM

Joseph Chirilov said:

Part of the CTP/Beta process is to get feedback on how much richness users can add using the current feature set. We look forward to getting your detailed feedback after you’ve had a chance to use the product. Thanks.

# October 29, 2009 3:32 PM

Billy Gee said:

Will this be a feature on Access 2010 pivot tables, which I have not been as fond of as Excel's, as well - will I still be able to link into an Access database with this functionality?

# November 2, 2009 2:09 PM

Joseph Chirilov said:

Billy: PowerPivot works only within Excel.  It can easily link to data in Access databases, however.

# November 2, 2009 3:54 PM
New Comments to this post are disabled
Page view tracker