Hi All,
I originally created a PowerPivot in Excel 2010. I was attempting to pull tens of millions of rows from SQL. I ended up upgrading to Excel 2013 because of the size limitations in Excel 2010. Before I switched to 2013, my boss and I met with our IT department and said there shouldn't be any issues using an Excel 2013 PowerPivot on our SharePoint 2010 (my company is very new to PowerPivot and unfortunately we are all learning together as we go).
Once I rebuilt the file in 2013 and uploaded it to SharePoint, I was unable to schedule a manual file refresh and the slicers do not work. Unfortunately we learned after the fact that there are indeed compatibility issues with SharePoint 2010, Excel 2013 and our SQL2008R2. Our IT department recommended creating the file again in Excel 2010 and using that for SharePoint. This will not work, however, because of the amount of data we need to pull. We've condensed our SQL queries as much as possible and Excel 2010 still crashes every time we attempt to use it.
At some point in the future, we will upgrade to SharePoint 2013 (although no one knows when, so I'm not optimistic). Does anyone have any suggestions for workarounds? I would really appreciate any thoughts!
Thanks!
Jessica
I originally created a PowerPivot in Excel 2010. I was attempting to pull tens of millions of rows from SQL. I ended up upgrading to Excel 2013 because of the size limitations in Excel 2010. Before I switched to 2013, my boss and I met with our IT department and said there shouldn't be any issues using an Excel 2013 PowerPivot on our SharePoint 2010 (my company is very new to PowerPivot and unfortunately we are all learning together as we go).
Once I rebuilt the file in 2013 and uploaded it to SharePoint, I was unable to schedule a manual file refresh and the slicers do not work. Unfortunately we learned after the fact that there are indeed compatibility issues with SharePoint 2010, Excel 2013 and our SQL2008R2. Our IT department recommended creating the file again in Excel 2010 and using that for SharePoint. This will not work, however, because of the amount of data we need to pull. We've condensed our SQL queries as much as possible and Excel 2010 still crashes every time we attempt to use it.
At some point in the future, we will upgrade to SharePoint 2013 (although no one knows when, so I'm not optimistic). Does anyone have any suggestions for workarounds? I would really appreciate any thoughts!
Thanks!
Jessica
