Separate projects to support datamarts?

[Saf2003]

Hi,

We have a project which is quite big and contains lots of reports. We plan to spit this up into separate reporting areas by subject and have separate projects for each subject area. However these datamarts share a lot of the same dimensions. Is there a way to have a core project which contain the schema description for the enterprise-wide data warehouse and separate datamart projects which just contain public object and are linked to the core project for the schema?

Has anyone else found a good solution for handing datamarts without having to manage load of different sets of metadata?

Regards, Saf

 

[reisw]

The only thing I can think of is to have one core project that just contains all schema objects that you use as a source for the other two projects. Whenever you make a change to a schema object you then copy it to both of the other projects. Not a great solution but I haven't heard of any other way of doing it. If it's not critical you could always have just one project and then put your subject areas into different folders. You could then use security to determine who gets to see which subject area.

 

[Saf2003]

This was the conclusion I had reach too. Thanks for the advise.