Databases
StackOverflow2013
Postsdbo
POHow to model a fact table
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to model a fact table
    primarykey
    data
    text
    <p>I'm about to create a data warehouse with facts and dimensions in a star-schema.</p> <p>The business questions I want to answer are typically these:</p> <ul> <li>How much money did we sell for in Q1?</li> <li>How much money did we sell for in Q1 to females?</li> <li>How much money did we sell for in Q1 to females between age 30-35?</li> <li>How much money did we sell for in Q1 to females between age 30-35 living in new york?</li> <li><p>How much money did we sell for in Q1 to females between age 30-35 living in new york?</p></li> <li><p>How much money did we sell for in category clothes last year?</p></li> <li>How much money did we sell for of the product blue jeans last year?</li> <li>How much money did we sell for of the product blue jeans to males between 40-42 living in Australia last year?</li> </ul> <p>I am thinking of a date dimension with the granularity of an hour (specifying year, month, day, hour, quarter, name of day, name of month etc.) I am also thinking of a product dimension and a user dimension.</p> <p>I wonder if these questions could be answered using a single fact table or if its proper to create multiple fact tables? I am thinking of a table such as:</p> <p><strong>FactSales</strong></p> <p>DimDate - fk to a table containting information about the date (such as quarter, day of week, year, month, day)</p> <p>DimProduct - fk to a table containing information about the product such as (product name)</p> <p>DimUser - fk to a table containing information about the user such as (age, gender)</p> <p>TotalSales - a SUM of all sales for those particular date,product and user.</p> <p>Also, if I would like to measure booth the total sales (money) and the total number of sales? Would it be proper to create a new fact table with the same dimensions but using TotalNumberOfSales as the fact instead?</p> <p>Thankful for all input I can get about this.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USPatrik
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to model a fact table
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMaybe "DimCustomer" would be more appropriate naming than "DimUser"?
      singulars
      1. POHow to model a fact table
      1. UStobixen
    2. COyes, thank you!
      singulars
      1. POHow to model a fact table
      1. USPatrik
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload