Painted into a healthcare DW "digital corner" -- or is it wrong to have keys and attributes in a single table
pzajkowski at 15h24
20
Jan
2011
Painted into a healthcare DW "digital corner" -- or is it wrong to have keys and attributes in a single table
Here's the short version: Is it OK to have a table which contains keys from other dimensions AND includes additional fields for attributes? (Is this a dimension, outrigger, factless, or merely unusual or just wrong?)
Here's the long version (with background information):
I've been maintaining a healthcare guidel
Here's the short version: Is it OK to have a table which contains keys from other dimensions AND includes additional fields for attributes? (Is this a dimension, outrigger, factless, or merely unusual or just wrong?)
Here's the long version (with background information):
I've been maintaining a healthcare guidel
About
This topic belongs to the forum
Data Warehousing and Business Intelligence based on dimensional modeling and the Kimball Lifecycle.
- Numbers of topics : 1858
- Numbers of messages : 8714
- Numbers of users : 3801
- Numbers of points : 1672
Similar topics
I'm trying to figure out how to best model a DataWarehouse Star Schema structure to capture certain medical information that will answer the questions we ask.
First the questions to put in some context:
1) How many distinct patients had a BMI in the
We have a CustomerAddress dimension table that will have a surrogate key assigned only. The customer address information will come down on both the CustomerOrder and CustomerShipmentInfo files (Bill To Customer and Ship To Customer). We have never had a
Hi,
Let's say we have a fact table: FactReceipt
which contains all our receipting transactions that occur during the month,
we may have 5 receipts of different types during one month for one contract.
Now let's say we build another fact table that
It is a data warehouse optimization project and a very basic data warehouse is in place. There are a couple of dimensions with only 2, 3 columns only (<30 rows) and where the Business key can be easily interpreted.
Ex: Event_Type_DIM: this has 2
We're an Oracle 10g warehouse site and still get nervous when adding new attributes to our ageing dimensions. The issue stems from not being able to reorder columns in Oracle. So your new attributes either sit at the bottom of the table (not good) or yo
Forums from same category
HmongThoobNtiajTeb. com/
Free forum : hi. Free forum : 2709rsgamboa6219. Free forum,
LEGO Island Discussion, modding, news and more!
Free forum : Forum IT Teknik Komputer dan Jaringan SMKN 1 SLAWI
Techy Boards, a growing technology discussion forum! For fans of nintendo, xbox, playstation or anything else!
Search
Informations
2 Replies For the topic :
"Painted into a healthcare DW "digital corner" -- or is it wrong to have keys and attributes in a single table"
This topic has been viewed 930 times.
Last message :
20/01/2011 at 15h24 by "pzajkowski"





