Comments on: Memory Considerations in PowerPivot http://powerpivotgeek.com/2010/02/03/memory-considerations-in-powerpivot/ An adventure in managed self-service computing Sun, 22 Jan 2012 01:58:55 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Memory Considerations in PowerPivot « PowerPivot Twins! http://powerpivotgeek.com/2010/02/03/memory-considerations-in-powerpivot/comment-page-1/#comment-386 Memory Considerations in PowerPivot « PowerPivot Twins! Sun, 14 Feb 2010 04:54:43 +0000 http://powerpivotgeek.com/2010/02/03/memory-considerations-in-powerpivot/#comment-386 [...] Read more… [...] [...] Read more… [...]

]]> By: Marco Russo http://powerpivotgeek.com/2010/02/03/memory-considerations-in-powerpivot/comment-page-1/#comment-353 Marco Russo Fri, 05 Feb 2010 08:38:59 +0000 http://powerpivotgeek.com/2010/02/03/memory-considerations-in-powerpivot/#comment-353 Thank you Dave. Regarding memory considerations, I added a post about specific investigations on table denormalization. All feedbacks are welcome. http://sqlblog.com/blogs/marco_russo/archive/2010/02/04/table-denormalization-study-in-powerpivot.aspx Thank you Dave.

Regarding memory considerations, I added a post about specific investigations on table denormalization. All feedbacks are welcome.

http://sqlblog.com/blogs/marco_russo/archive/2010/02/04/table-denormalization-study-in-powerpivot.aspx

]]> By: powerpivotgeek http://powerpivotgeek.com/2010/02/03/memory-considerations-in-powerpivot/comment-page-1/#comment-352 powerpivotgeek Thu, 04 Feb 2010 22:55:35 +0000 http://powerpivotgeek.com/2010/02/03/memory-considerations-in-powerpivot/#comment-352 Unfortunately the limit is the storage mechanism in SharePoint; not the upload process itself. If you look at the schema for the SharePoint content database you will see that the actual *file* contents are stored as a sequence of blobs -- which the SP OM knows how to string together into the final results of the file when uploading/downloading. It uses 32-bit signed integers as offsets into the content -- which is where the 2GB limit comes from. It is an artifact of the file at rest. _-_-_ Dave Unfortunately the limit is the storage mechanism in SharePoint; not the upload process itself. If you look at the schema for the SharePoint content database you will see that the actual *file* contents are stored as a sequence of blobs — which the SP OM knows how to string together into the final results of the file when uploading/downloading. It uses 32-bit signed integers as offsets into the content — which is where the 2GB limit comes from. It is an artifact of the file at rest.

_-_-_ Dave

]]> By: Marco Russo http://powerpivotgeek.com/2010/02/03/memory-considerations-in-powerpivot/comment-page-1/#comment-347 Marco Russo Thu, 04 Feb 2010 08:32:23 +0000 http://powerpivotgeek.com/2010/02/03/memory-considerations-in-powerpivot/#comment-347 Dave, I'd like to know if we can overcome this limit by: 1) Saving a "small" version of data in SharePoint, for example by using a view which filters only a part of data from the data source 2) Changing the view on SQL Server by removing the filter condition 3) Refreshing the PowerPivot data on SharePoint with a scheduled action - at that point, the workbook should be processed by SSAS engine, but will it be saved on SharePoint? In other words, is the limit just for upload or for internal storage? Marco Dave,

I’d like to know if we can overcome this limit by:
1) Saving a “small” version of data in SharePoint, for example by using a view which filters only a part of data from the data source
2) Changing the view on SQL Server by removing the filter condition
3) Refreshing the PowerPivot data on SharePoint with a scheduled action – at that point, the workbook should be processed by SSAS engine, but will it be saved on SharePoint?

In other words, is the limit just for upload or for internal storage?

Marco

]]>