Other than copying and pasting the text from the script view, is there any way to share calculated members between cubes
I have two cubes that have some common facts, and would like to be able to point both at the same script for calculated members, so that any changes only have to be made in one place.
Thanks,
Sam
Share calculated members between cubes
Steve from adzac
You cant share calculations from one cube into another.
The situation you describe begs another question: If you build two cubes based on the same data, may be you should be looking into creating a single cube with all dimensions and use Perspectives feature to provide your customers with two different views into your cube.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
hazz
It is bit strange. You should be able to use perspectives to hide measures you dont need.
In Analysis Services 2005 you should try and consolidate your cubes into the single one, it simplifies modeling, simplifies management. Provides a single source of data for client applications.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
provato
Thanks for answering Edward. I agree with your comments, but I have had trouble working my data into one cube successfully.
In the solution I am working on, I have different lines of business which have the same facts, but different details in one of the dimensions. I can combine the dimension tables using union views on the data warehouse, but the problem I have with perspectives is that although I can hide the attributes that don't relate to a certain line of business, I cannot filter the data, so a perspective for one line of business still contains the facts for all lines of business.
I have tried various approaches, and have settled for now on having a different cube for each line of business, which all look at the same fact table, and at different views on the dimension table. This filters the fact data automatically, as the dimension table only contains the records for the relevent line of business. Of course, it does mean that I need to have all the calculation code in more than one place.
Do you think there is a better way to approach this
Sam