When to combine facts from different systems...

View previous topic View next topic Go down

When to combine facts from different systems...

Post  2by4 on Mon Jul 23, 2012 10:09 am

Hello, I'm having a heck of a time wrapping my head around some of these concepts, neither way that I'll think of seems better or worse
to me:

We're a physical & electronic newsletter publisher. We have 2 systems, the physical system stores subscriptions when they start/end money paid etc.
In the case of print newsletters, the start/end is determined by issues remaining.

We also offer free ezines, these subscriptions have start dates, but no end dates, no issues no money paid.

I've modeled the "product" dimension to contain both types of product pretty easily, it makes sense in my head. However, some of the FACT tables are muddier to me.

For example, one of the facts is "issue sent" (a physical in the mail issue), which issue number, to who & when etc.

There is a similar fact in the email side, 'email sent' for the free ezines.

I can think of a way to combine them both into 'issue sent' but should I?

Should I treat those as separate facts? I'm unclear as to the pros/cons.

Any thoughts appreciated, I can provide more details if this is too unclear.

Thanks!

2by4

Posts : 5
Join date : 2012-06-25

View user profile

Back to top Go down

Re: When to combine facts from different systems...

Post  ngalemmo on Mon Jul 23, 2012 4:01 pm

Just a guess, but I would assume the dimensionality is different between the two. I would probably go with separate facts at the atomic level. You can always build an aggregate that combines the two at some level to make general reporting simpler.
avatar
ngalemmo

Posts : 3000
Join date : 2009-05-15
Location : Los Angeles

View user profile http://aginity.com

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum