Refreshing I-Cubes & Dynamic Sourcing

Refreshing I-Cubes :  

we can refresh the I-cubes in 2 ways.

1.     scheduling I-cube 
2.     Creating incremental refresh report for the particular I-Cube

Scheduling I-Cube :  we can specify when I-cube should refresh based on time based trigger / event based trigger.
Incremental refresh I-cube :  It is available from Mstr version 9.2.x, using this we can specify the when I-cube should be refresh based on the things..

Insert
Delete
Update
Update Only.

we can update it manually also , right click on the I-cube and select run (updating).

Dynamic Sourcing :

Dynamic sourcing is available from 9.2.x, we can enable / disable this feature in project configuration wizard. once we enable the dynamic sourcing the reports might be get the data from I-cubes without we link the report to particular I-Cube.

No need to link the reports, Small example :

I-Cube1 Objects are :  Attributes : A,B,C,J & Metrics : E,F,K
I-Cube2 Objects are :  Attributes : A,B,C,D,Y,Z & Metrics : E,F,G,H,I

suppose we run the report1 having the  attributes  A,B,C,J & Metrics : E,F,K obviously it gets the data from I-Cube1.  (Note : we didn't link this report to I-cube, due to dynamic sourcing feature it is getting the data from I-cube rather than database)

suppose we run the report2 having the attributes A,Y,Z & Metrics : E,G,H obviously it gets the data from I-Cube2.

suppose we run the report3 having the attributes A,Y,Z,L & Metrics : E,G,H,O obviously it gets the data from Database because same attributes / metrics are not published yet in I-Cube.