Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago
Solved

best table setup to begin a Ticket based data model

Hello everyone,

 

This is my first data model & I would like to have some advice on best table setups before doing any calculation.

 

I have a classic, fact table with one row per ticket with a status + extra details & also  4 different dates dimensions I need to use to calculate basic aging but also some advanced aging flagging based on different criteria contained in the model.

I have a calendar table with all the details i need & that i can replicate if need be.

The aging will need to be calculated between creation date & close date (some tickets won't have a close date).

 

I want to be able to use any relative date to have a view of my open pipeline of tickets to date, my average versus last year, last Q, etc ...

 

Now, what I need the help of the community for is to understand if i need to break down the fact table calculate the status & aging of my cases the best & clean way possible or not .... & what kind of relationship i need to create between my calendar(s) & my table(s) for a basic calculation.

 

Thanks in advance for any feedback.

4 Replies