python (65.1k questions)

javascript (44.2k questions)

reactjs (22.7k questions)

java (20.8k questions)

c# (17.4k questions)

html (16.3k questions)

r (13.7k questions)

android (12.9k questions)

Questions - fact

Not sure whether to model Tickets as a Fact or Dimension

I have a source with information about TICKETS and about TIME_ENTRIES. Initially I wanted to model TICKETS as a fact table with measures like first_response_time, resolve-time, and with dimensions lik...
test-img

Bart Jonk

dimensional-modeling

star-schema

fact

kimball

Votes: 0

Answers: 1

Latest Answer

The standard approach is to identify your measures and then define the grain for each measure. If measures have the same grain you can, but don’t have to, put them in the same fact table. If measures ...
test-img

NickW

resolve the ambiguity for the dimensional model for one to many(fact to dimension) ratio

I have a question regarding facts and dimensions. suppose I have come across a fact table fact_trips - composed of columns like trip_id , driver_id, vehicle_id, date ( in the int form - 'YYYYMMDD') , ...
test-img

AdityaT101

data-warehouse

dimensional-modeling

fact

Votes: 0

Answers: 1

Latest Answer

TripAlerts is a fact, not a dimension. So you have a table: FactTripAlert with primary key (TripId,AlertId).
test-img

David Browne - Microsoft

The ambiguity w.r.t date field in Dim_time

I have come across a fact table fact_trips - composed of columns like driver_id, vehicle_id, date ( in the int form - 'YYYYMMDD') timestamp (in milliseconds - bigint ) miles, time_of_trip I h...
test-img

AdityaT101

time

data-warehouse

dimensional-modeling

fact

Votes: 0

Answers: 1

Latest Answer

You should have 2 Dim tables: DIM_DATE: PK = YYYYMMDD DIM_TIME: PK = number. Will hold the same number of records as however many milliseconds there are in a day (assuming you are holding time at the...
test-img

NickW

Posts

Questions

Blogs

Jobs