June 17, 2009 at 12:48 pm
We are weighing the pros and cons of building one huge "Operations" cube as opposed to building a handful of cubes and then creating a linked cube to bring them all together. For example, our existing Forecast cube uses the InventoryFact table for a measure group. A proposed Manufacturing cube will use the same InventoryFact table, but the manufacturing data is not necessarily directly related to the Forecast cube data elements. However, we can see the potential of having both data elements on a report some day.
We are trying to answer the question, is it better to have one huge cube containing all the measure groups and dimensions or a few smaller cubes connected together with a linked cube. Can someone please give us their opinion or share their experiences?
FYI - We are using SQL 2008 and have not built a linked cube before. We do however have other cubes in production in separate databases not necessarily related to this project.
Thanks
Chris
June 17, 2009 at 2:00 pm
Please don't cross post. It just wastes peoples time and fragments replies.
No replies to this thread please. Direct replies to: http://www.sqlservercentral.com/Forums/Topic736889-17-1.aspx
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply