sql server - DW Factless Fact Table w/ Transactional Free Form Fields -


i reconstructing factless fact table transaction table. there obvious shared dims org, status, service, serviceaction, send date, etc. however, there 2 issues i'm trying work through:

  1. on transaction table there free form entry fields values phone, email, chkbxrequestreceipt. directly related transactionkey. if pull these fields out of fact table own dim, creates 1-1 dim-fact relation not seem correct.

  2. the serviceaction dim 1 field on fact table broken out 3 different dim tables. done because services share no common fields. there 1 transaction every serviceaction. sum of rows in 3 service tables = total rows of transaction table.

could offer advice on best way model this?

  1. you can consider phone, email, chkbxrequestreceipt degenerate dimension (or multiple degenerate dimensions). degenerate dimensions dimension without dimension table. have degenerate dimensions when fact table has transaction level grain.

  2. about 3 tables serviceaction. suggestion put them in same dimension table, understand have table lot of nulls. if write reports manually 3 tables aren't problem, if use tool leverages dimensional model generate automatically sql code, need have single dimension table.

you can think have 3 different dimensions share same column on fact table, work, can bit confusing business users, if can create own reports. anyway in case need create forth dimension allserivceaction in case need create report want show calls , information serviceaction


Comments

Popular posts from this blog

node.js - Mongoose: Cast to ObjectId failed for value on newly created object after setting the value -

[C++][SFML 2.2] Strange Performance Issues - Moving Mouse Lowers CPU Usage -

ios - Possible to get UIButton sizeThatFits to work? -