DW design problem

[JCHAMORRO]

Hello all,

We have developed a dw for ove 2 year, and now we new a new design in order to give enterprise solutions and queries. I have read a lot about diferent implementations all around star schema whit fact tables and it´s dimensions .
This is our purpose, but the problem is that we need to offer multiple relations and that force us to cross fact tables and we don´t want that.

For example:
Actually we have:
*A fact customers table
*A fact Instalations table
*A fact problems table

We new to sort out, the customers in a fixed state that have instalations with problems.

As we are now we need multiple fact crosses, how could we implement this to avoid this backdraw.

Thanks a lot.

 

[SansTime]

Hi,

I've heard recently about something called The Matrix Methodology, and inside their there's an interesting piece called the Data Vault.

It sounds like this may be the missing component you're looking for.

It's a data modeling technique (brand new to the DW scene) which allows full-DW capabilities. It stores massive amounts of detailed information in the lowest available granular form. It does this in also the smallest possible physical space. It's an interesting solution beginning to break in to the world of DW... I just heard about it myself.

Stay Cool

 

[Edimator]

SansTime, were i can get more info about the Matrix Methodology, and if that is like star schema or snowflake schema.

Thanks!

 

[SansTime]

You can find out more about The Matrix Methodology at:

http://www.coreintegration.com.

Click on Methodology.

I found out that it's an implementation strategy, a how-to guide to building data warehousing systems - reliably, repeatably.

About the Data Vault, you'll have to ask someone at that company for more information...

Stay Cool