April 16, 2009 at 12:47 am
Is there any way to process cube without affecting end users seeing reports...
April 16, 2009 at 5:30 am
You can look at minimizing the downtime or trying to eliminate it all together. When processing the cube you can look at only processing the changed data and using partitions within your measure groups to limit the amount of data that you are processing (like only current quarter, month, or week) instead of the entire measure group or cube.
Other things you can look at would be using a second instance. You can run this on the same server if you have adequate hardware. You can then have a Reporting and a Processing instance and once the processing is complete you can synchronize the Reporting instance with the changes and this will not impact the end-users except for the cache having to get updated again.
Another option would be to implement Proactive caching to load the changes from the source. Both partitioning and proactive caching would be Enterprise features, so not sure what edition you are using. Going the synchronization route would probably be your best option.
Analysis Services Synchronization Best Practices
SQL Server 2005 Analysis Services Processing Best Practices
How To Implement Proactive Caching in SQL Server Analysis Services (SSAS) 2005
How To Define Measure Group Partitions in SQL Server Analysis Services (SSAS) 2005
----------------------------------------------------------------------------------------
Dan English - http://denglishbi.wordpress.com
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply