THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

SQLBI - Marco Russo

SQLBI is a blog dedicated to building Business Intelligence solutions with SQL Server.
You can follow me on Twitter: @marcorus

PowerPivot Compatibility across versions

There are several versions of PowerPivot available and starting with Excel 2013 there are also several versions of Excel. It is useful to look at the compatibility between the different versions of Excel and PowerPivot available now.

As a general rule when you have a PowerPivot workbook saved with a specific version of PowerPivot:

  • You can upgrade a workbook to a newer version of PowerPivot
  • You can upgrade a workbook to a newer version of Excel
  • You cannot open a workbook using a previous version of PowerPivot
  • You cannot open a workbook using a previous version of Excel, if it contains PowerPivot data

First caveat: you can open an Excel 2010 workbook containing a PowerPivot data model in Excel 2013, but once you save it in Excel 2013, you can no longer open it in Excel 2010. This is because a different file format for PowerPivot data used by Excel 2013 that cannot be understood by Excel 2010.

Second caveat: A file saved in Excel 2010 with PowerPivot 2012 (RTM or SP1) cannot be opened by an Excel 2010 running PowerPivot 2008 R2.

Each workbook has a compatibility level for PowerPivot data that corresponds to the PowerPivot version used to save the data. Here is the list of currently available compatibility levels:

  • 1050 (2008 R2)
  • 1100 (2012 RTM/SP1)
  • 1103 (Excel 2013)

The following table tells you what happens when you try to open an Excel 2010 file in a certain compatibility level (columns) with a certain version of PowerPivot (rows):

 

1050

1100

2008 R2

Read/Modify

Not Supported

2012 RTM

Read/Upgrade++

Read/Modify

2012 SP1

Read/Upgrade++

Read/Modify/Upgrade

++ It is important to call out that it is *not* supported editing 1050 PowerPivot models in the 2012 release – you *have to* upgrade the model to 110x before you can edit/refresh the model.

A detailed list of errors you can have opening different a workbook with a different compatibility level than the current version of PowerPivot you have is available in the article Version compatibility between PowerPivot Data Models in Excel 2010 and Excel 2013. As the article mention, PowerPivot for SharePoint can open PowerPivot workbooks of previous compatibility levels, but in order to upgrade the data on the server (scheduling a data refresh) you need to upgrade the workbook to the newer format.

You have to be careful using PowerPivot in mixed environment, especially when you want to share an Excel file containing PowerPivot data. Once you refresh PowerPivot data, you need to upgrade the compatibility level if you opened the workbook with a newer version of PowerPivot, and once you do that, your colleague with a previous version of PowerPivot can no longer open the same workbook. Saving the file on SharePoint makes it possible to navigate into data, but you need a correspondent or newer version of PowerPivot on SharePoint than that used to save the file.

For these reasons, when we provide the examples for our PowerPivot Workshop and our book for Excel 2010, the sample files are saved with the older version of PowerPivot (2008 R2). Now that we are working on the Excel 2013 version of the book and of the workshop (soon to be available!), we are finally going to release samples using a newer version of Excel and PowerPivot.

Published Monday, January 14, 2013 2:44 PM by Marco Russo (SQLBI)

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Chien-sheng Tsai said:

Bought several different PowerPivot books and trying to learn, but have not been too successful.  In spite of the hype and all the books written by so many authors, PowerPivot just does not seem ready for prime time use.  The idea is good, but so many issues, and so much time required to track errors down--almost not worth the trouble--and now find it difficult to trust PowerPivot.  

I am in a learning mode, so not mission critical.  If I were to rely upon PowerPivot to build a real application, it would be problematic.  

So much promise heralded in the books, and such potential, all wasted in the poor execution.  Good thing it is a free add-in.  Very disappointing.  No wonder the other vendors are still doing well.  MS had potential of being # 1 in self-service BI with PPVT, if it worked well.  

I am running Excel 2010 32-bit on Vista 64-bit with 16 GB RAM and Quad-Core CPU, so it is not that my machine is inadequate.    

amount of interest

April 18, 2013 1:22 AM
 

Marco Russo (SQLBI) said:

Thank you for the feedback.

In order to be useful (for articles and book), can you be more specific about the reasons why you are not successful using PowerPivot?

Is this because of DAX Language, some bug in the product, some limitation in calculation and/or data modeling, ... ?

What do you see in other product that is better in this regards?

Thanks again,

Marco

April 18, 2013 3:21 AM
 

Kuba said:

Hi Marco,

my name is Kuba and I hope you could help me with issues I encounter with Powerpivot. I created a report based on a simple data model. It has a significant amount of data, however I thought it is still acceptable from Powerpivot perspective. The file is around 100MB.

I use a machine with 8 cores and 16 GB of RAM. However, if I start playing with different attributes from data and move them around ROWS, COLUMNS and FILTERS, I end up with Excel eating almost 15GB of RAM. Then, I start receiving strange errors in Powerpivot about expired sessions etc. It seems as if the tool was quite unstable. What I also noticed is that Excel does not release the memory. It does not matter if the report has complex layout and filters or it is as simple as possible - Excel will occupy those 15BB of RAM as long as I reopen the file. Any ideas why it is like that? Is it a memory management bug?

Greetings,

Kuba

May 17, 2013 5:09 PM

Leave a Comment

(required) 
(required) 
Submit

About Marco Russo (SQLBI)

Marco Russo is a consultant, writer and trainer specialized in Business Intelligence with Microsoft technologies. He runs the SQLBI.COM website, which is dedicated to distribute resources useful for BI developers, like Integration Services components, Analysis Services models, tools, technical information and so on. Marco is certified as MCT, MCDBA, MCSD.NET, MCSA, MCSE+I.

This Blog

Syndication

Archives

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement