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


Loading Fact Tables - Step by Step Instructions Challenge


Loading Fact Tables - Step by Step Instructions Challenge

Author
Message
sneumersky
sneumersky
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2168 Visits: 487
Simply put, your measurement events appear to be:

1. Getting consent (possibly)
2. Taking a course (definitely)

Those events give context to the employee (working in a dept that is part of an ogranization) via a status (that can change based on the number and type of courses taken)? Can the status change and move along finite milestones such as "Not Certified", Certification in Process", "Partially Certified", "Fully Certified"?

The end goal is compliance, which is based on a status Fully Certified in different areas of study such as "Slip and Fall"?
marvin.perrott
marvin.perrott
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: 212
This is correct. My compliance can move through finite steps, however it has to be based on a set of courses having a 'Completed/Passed' status.
sneumersky
sneumersky
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2168 Visits: 487
Is it important to go back in time and ask:

"What was the compliance status of the department back on 1/1/2009?"

Or, do your end users merely care about there "here and now" state of an employee's status?
marvin.perrott
marvin.perrott
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: 212
Yes, it is important to know previous years deparment's compliance for comparison and trending and later on predictions.
sneumersky
sneumersky
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2168 Visits: 487
Would you say the trending is fixed (as in merely year to year)? Or, do the end users need to be able to compare any periods to any periods (i.e. this quarter to last year, this month to last month, etc)?

Also, is there a percentage compliance or a Key Performance Metric you must meet (say 80% Cardiac Nurses must be compliant by 2014--or "employee X must be 100% compliant by the end of the quarter or they're outta here!")? Are those metrics published at all?

There are some designers that would put all the employee's compliance buckets into columns in the employee dimension (if those buckets were fixed) and, as part of the ETL process, update those buckets based upon the courses taken (courses stored in the fact table) or not taken (courses required but not existing in the fact table). It's called the "When A Dimension Becomes A Fact" concept.

Joy Mundy of the Kimball Group wrote a nice concise article. In relating to this article, think of your employees as the entity and the courses taken as the measurement event.

http://www.kimballgroup.com/2011/11/01/design-tip-140-is-it-a-dimension-a-fact-or-both/
RonKyle
RonKyle
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1290 Visits: 3344
tinyint is one byte, smallint is 2 bytes. Review how many values you can have for each (256 and 65K+ respectively) and use the right one for every dimension.


I support this concept, but at least in SSAS 2005 the tinyint can't be made into a connection in the DSV. So I avoid it even if it would have been a good choice. For those, the smallint isn't much of an increase and allows you to use negative numbers for the Unknown and (if needed) Not Applicable Bucket.



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