SQL Server 2005 datacube processing in high transaction system
Dimensions need to have all the values that the cube has. To avoid having cube value that doesn't exist in the dimensions, I did the following:


have a separate database as a staging database
periodically fill this staging db with data from transaction db
the cubes are generated from this staging db
dimensions are refreshed first, then the cubes
NO data modifications in the staging db between refreshing dimensions and refreshing cubes