Reporting strictly on a dimension

Go down

Reporting strictly on a dimension

Post  ryno1234 on Wed May 13, 2015 9:12 pm

Dimensions offer a lot of information to report on and with the inclusion of effective / expiration dates, they also offer a view of events over time. This makes it possible to offer interesting information without the use of a fact table.

As I'm actively dealing with "employees" right now, I'll use them as an example: An employee's job title may change over time, thus we stamp a new dimension record and update the previous records effective / expiration dates.

In this situation, I could figure out how many employees were in each job title for any given day without the need of a fact table.

What is the general stance on this?

Posts : 33
Join date : 2015-01-07

View user profile

Back to top Go down

Re: Reporting strictly on a dimension

Post  ngalemmo on Wed May 13, 2015 10:29 pm

Yeah you could, but that is not dimensional design. And maybe you can answer that particular question, but what about other analysis? How difficult would it be to construct any query relating to an employee's tenure or staff turnover?

The basic design principle is to separate things into business events or states (facts) and their contexts (dimensions). A properly designed star schema allows a user to perform all manner of analysis of the data using a simple, repeatable query pattern.

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

View user profile

Back to top Go down

Back to top

- Similar topics

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