Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Fact and dimension structior for Ticket tracking


Fact and dimension structior for Ticket tracking

Author
Message
agnetha_11
agnetha_11
Grasshopper
Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)

Group: General Forum Members
Points: 13 Visits: 107
Fact and dimensional structure for Ticket tracking (Sorry can't edit the topic)

Hi,

I am new to Dimensional modeling and SSAS reporting. I am working on creating a cube but first I have to create the fact and dim tables.

I have to keep track of the status of tickets, dates they were opened and closed, operator that worked on the ticket, count of the tickets, the duration in days the ticket was open before it closed, and the # of tickets per customer.

Tables

FactTicket: Count for ticket, duration of ticket, status of ticket,
DimDate
DimCustomer
DimOperator: Operator_id, type, ticketcode

Please let me know if I should add any more dimtables. Any suggestions or advice is appreciated.

Thanks.
Bruce W Cassidy
Bruce W Cassidy
Right there with Babe
Right there with Babe (787 reputation)Right there with Babe (787 reputation)Right there with Babe (787 reputation)Right there with Babe (787 reputation)Right there with Babe (787 reputation)Right there with Babe (787 reputation)Right there with Babe (787 reputation)Right there with Babe (787 reputation)

Group: General Forum Members
Points: 787 Visits: 1033
You may need a time dimension (it's a bit of a modellers choice, and I'd probably err with just storing the time as part of the fact).

I would also suggest you would need a status dimension. It's probably fairly small and could form a part of a generalised "status" dimension across multiple facts.

You may also need two fact tables: one for tracking who worked on it and one for tracking when it changes state. Again, it's a modellers choice, but I find in practice those are two very different things for reporting purposes, so often it's a good idea to model them separately and make the subsequent reporting easier.

Some ideas anyway; I can't suggest more without seeing more of the data mix and the reporting requirements.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search