two facts that relate via degenerate dimension
Hi, I have a order line fact which look like this: Order Line Fact ------------- Order Line Key (SK) Order Line number (DD) Order Number (DD) Some measure (fact) Now some time later I have another fact which would reference the Order Number

use of degenerate dimension to physically join two logically related fact tables
I am looking for a sanity check on a design decision. Here is the scenario: The business domain is insurance, specifically life and annuity. I have two fact tables - factPolicyTransaction and factCommissionTransaction. Policy transactions,

many to many relationship between dimension level
I need help to design dimension model. Detail of Dimension are as following: Dimension : Student, School Fact : Grade 1. Class_Year 2. School 3. Area 4. City Analysis Requirement are to drill up /down by above given hierarchy there is : M:1

Evening, 24 May; on deck
Form demanded that he report the action of locking a Marine in the irons. Temper suggested that he forget it. Disgust at the whole affair ultimately drove him to present himself at the wardroom to see Lieutenant Cartwright. The sooner he was absolved of

Should I use a degenerate dimension or create a junk dimension?
Hi everyone, I have a FACT table that contains reforecast data. Reforecasts are part 'actual' transaction data, part 'budgeted' data, both of which are stored in the same reforecast FACT table. I want to add a bit field to the FACT table to distinguish

Degenerate Dimensions
Hi there, I have come across a situation where my Fact table contains a degenerate 'Claim Number' column. This is fine, but I have discovered that some of the incoming data to populate my fact table do not have a claim number. How should I handle this

CHEAP EGRB 102 book Electric Circuit Fundamentals
contact williamskl5@vcu.edu to buy this book for $50. (It retails at over $100)

Opinion on Jeggings??
hmmm I have a mixed opinion on jeggings... some girls look really hot in them.. makes their bum's look great! Others i'm not so sure :\.. they just don't suit some people! Thoughts?

HMS Surprise deckplans
Huzzay! Someone has resurrected the wonderful lost website! The Ships of Jack Aubrey can be now be viewed again, with the wonderful clickable HMS Surprise deck plans here (being a frigate similar to our own Terpsichore.) edit: PS, Sharpie, I

HMS Terpsichore
HMS Terpsichore was a 32-gun Amazon-class fifth-rate frigate of the Royal Navy. She was built during the last years of the American War of Independence, but did not see action until the French Revolutionary Wars. She served during the French Revolutionary

Fallout: New Vegas
Hey guys, so with the release of this game in only a few hours. What are you guys most excited about?

Samsung Galaxy Tab car charger and travel charger
Sunpow unveiled charger kits for Samsung Galaxy Tab 1. Car charger for Samsung Galaxy Tab P1000 Input:12-24V; Output: 5V 2A, short circuit protection 2.Travel charger for Samsung Galaxy Tab P1000 Input:110-240V; Output: 5V 2A, short

Customer Age
Hi, Does anyone know the best way to model customer age? I guess there are 3 options: 1)Just their birth date, 2)Their current age as an attribute, 3)their age as an attribute but make it a type 2 scd so that you get all their age history. This is

Disadvantage of Fact table with 44 columns
Hi all, First of all this question my be super easy for you guys but I am new with data warehousing. Our fact table, let name it SALES_FACT has 296 million rows and 44 columns. Out of 44 column 36 columns are foreign key values joined to diffrent

Degenerate dimension & accumulating fact
I am currently looking at the design of an accumulating fact table that has order number as a degenerate dimension (the snapshot is one row per order). There are a few additional fields that apply to the order, that are also being carried as additional