Nov 9, 2010 - Microsoft announced new details about next version of PowerPivot
User Rating: / 6
PoorBest 
Written by PowerPivot-Info.com   
Tuesday, 09 November 2010 16:13

November 09, 2010 - At SQL PASS conference Microsoft announced new details about next version of PowerPivot.

Next version of PowerPivot will support:

  • KPIs
  • Perspectives
  • Multiple relationships
  • Hierarchies
  • Parent-child hierarchies
  • Many-to-many relationships
  • New DAX function RANK
  • Distinct count will be standard PowerPivot aggregation type
  • Drillthrough
  • Rich data types: BLOBs, images
  • Partitioning
  • Paging
  • Role-based security model using Active Directory
  • Row and column level security to secure data at the deepest level
  • Possibility to create BISM = BI Semantic model
  • In the next release you will be able to import PowerPivot workbook into BIDS 2010 environment and convert your PowerPivot workbook to enteririse level application by creating BI semantic model

Capture3_0

 

Capture4_0

  •  PowerPivot will be able to load data from Parallel Data Warehouse (PDW)
  • You will be able to build Enterprise Applications with PowerPivot using BIDS environment that will support security, partition management and other Enterprise level requirements
  • Next release of SQL Server will support columnar indexes. They are build on same technology as PowerPivot. These type of indexes will significantly increse relational query performanc.
  • Microsoft first time announced project "Crescent" - a new Web-based data visualization and reporting tool that extends PowerPivot.

Note: Some of the features listed above will work just with PowerPivot in BISM mode.

Additional information about project Crescent also can be found in following interview with Amir Netz:

 

Or if you have trouble seeing this interview here, use following youtube link...

Additional resources


 

 
Comments (1)
1 Wednesday, 04 May 2011 01:52
farg
I don't get the ability to "drillthrough" under a PP context (as opposed to a true SSAS cube context). In PP aren't you working with the data in both its raw (un-agg'd) detailed, sometimes summed forms, already? How are you drilling through, that concept only makes sense to me when you're looking at agg'd facts. What am I missing? Is it just a "snap-to all leaf" kind of label that just drops you to an all-leaf level of the current context of fact data?

Am the only one really f-ing confused by the BISM and PP, and the we're-depricating-SSAS statements, and the no-we're-not-depricating-SSAS-because-that-will-make-the-MS-practitioners-mad statements, and other baffling statements?

I can see adding capabilities beyond what a traditional cube can provide, but not if the goal is to undermine the whole current market and foundation of current implementers.

Greater products (and companies) have gone to pot when your market is confused as to what you're offering. They need to keep it simple becauese obviously the Windows juggernaut will not be able to fund these misadvantures for too much longer. And miffing your most prominent practitioners by confusion and obfuscations are only going to make for more skiddish buyers and will scare current MS BI supporters away from the platform. Maybe they don't care because it's self-serve?

Don't anyone tell me that there wasn't a technical way to extend a fundamental SSAS cube and provide backward compatibility. MS used to bend over backwards to keep prior technology working going forward...are they too arrogant, conceited, or lazy now?
 

Pyramid+PowerPivot