9/11 Class Flashcards

1
Q

design dimensional model

A
  1. user requirements - ask users about their most frequent queries
  2. existing data resources
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

precomputed attributes

A

we can have this in a datawarehouse but not in a database

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

warehouse key

A

unique identifier for the data warehouse data

every table must have one

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

design single fact dimensional model

A
  1. decide fact measurements
  2. decide grain of fact - level of detail
  3. Decide fact table
  4. Determine primary key for fact table
  5. decide key dimension tables for a fact table
  6. Decide analysis dimension tables for a fact table
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

factless fact table

A

is good for tracking an event

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

read chapters 3, 5, 12, 13

A

do it or at least the bold terms

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

aggregate fact table

A

additional table created to measure something

you don’t want too many aggregate tables

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

conformed dimension tables

A

a dimension table shared by fact tables
support drill across queries on star schema that help us find connections in data like amount of promotion versus sales
allows for more options to analyze data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

multi fact dimensional model

A

dimension tables
one warehouse key - primary key
dimension attributes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Step 1 decide facts and fact measurements

A
Fact 1: Sales
              Quantity 
              Price
              Shipping fee   
              Sales Amount = price * quantity
Fact 2:Promotion Cost
                Cost
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Step 2: decide grain of facts

A

find the record for the facts in your fact tables and find the lowest level of
sales - order line
promotion cost - product_promotion record

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Step 3: Decide fact tables

A
sales_fact
  quantity
  price
  shipping_fee
  sales_AMT
promotion_cost_fact
   cost
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Step 4: Determine Primary Keys of Fact Tables

A
find the natural keys that can uniquely identify records in fact tables and transform into warehouse keys
sales_fact
  #product_key
  #customer_key
  #orderdate_key
  *quantity
  *price
  *shipping_fee
  *sales_AMT
promotion_cost_fact
   # Product_key
   #Promotion_key
   *cost
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

key dimension table

A
connect the two fact tables with this key table
Product
   #product_key
   *PID
   *PName
   *PCName 
Promotion
  #promotion_key
  *PMID
  *PM_Name
  *PM_Date
Customer
  #Customer_key
Order Date
  #OrderDate_key
you cannot remove these tables
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Step 5: Decide key dimension tables for a fact table

A

above step

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Step 6: Decide analysis dimension tables for a fact table

A

see notes on canvas

17
Q

Step 7: Connect Separate dimension models using conformed dimension tables

A

see notes on canvas

18
Q

Multi-Valued dimension table tools

A

determine cardinality

19
Q

crows foot

A

means a one to many

20
Q

referer

A

tells what site you came from

21
Q

group bridge

A

solves many to many tables

22
Q

D7 Special dimensions

A

large number of indicators or flags left in the source data
Solution 1:
leave them unchanged in the fact table. This is bad because it makes the table very large and hurts performance
Solution 2:
making tables for every indicator. This is bad it causes a performance issue
Solution 3:
get rid of data = bad :)
Solution 4:
junk dimension: throwing all of the related indicators in one table this is the solution

23
Q

mini dimension

A

splitting large tables into smaller tables

24
Q

D8 Too few or too many dimensions

A
most dimension models end up with 5 to 15 dimension tables. this is how many should be in your product
questions to ask:
analysis dimensions
role playing dimensions
junk dimension
mini dimension
25
Q

local design tools

A

F1calculation
additive semi additive non additive fact attributes
factless fact table
aggregate

26
Q

local design tools

A
D's
1 Slowly changing dimension
2 time dimension
3 snowflake
4 roleplaying dimension
5 conformed dimension
6 multi valued dimension
7 special dimension(junk and mini)
8 too few and too many dimensions