datawarehouse modeling
3 posters
Page 1 of 1
datawarehouse modeling
I'm modeling data warehouse for some kind of helpdesk system also this si my graduate work and first project. Question i have is it possible to connect two fact tables. For example fact table Problem(FactProblem) stores informations about problems that customers have reported than it generates one or more work tasks. Work tasks are stored in FactRadniZadatak table. These facts have common dimensions like status, date, employee...
I want to be able to answer what tasks has foloving problem generated by drill down
Here is dw diagram
FactRadniZadatak -> worktask
DimDjelatnik -> employee
DimKlijent -> customer
DimTipGreske -> problem type
DimRazvojnoPodrucje -> department
DimPrioritet -> task priority
Thanks for replay
I want to be able to answer what tasks has foloving problem generated by drill down
Here is dw diagram
FactRadniZadatak -> worktask
DimDjelatnik -> employee
DimKlijent -> customer
DimTipGreske -> problem type
DimRazvojnoPodrucje -> department
DimPrioritet -> task priority
Thanks for replay
Tesla0306- Posts : 1
Join date : 2011-04-16
Re: datawarehouse modeling
Facts are combined by joining two sub-queries. Each sub query aggregates one of the fact tables along dimensions common to both fact tables. You then join the two aggregates.
Re: datawarehouse modeling
ngalemmo wrote:Facts are combined by joining two sub-queries. Each sub query aggregates one of the fact tables along dimensions common to both fact tables. You then join the two aggregates.
Hello ngalemmo,
Will this not be terrible on performance ?! I mean isn't it better/faster to just put it all in one big fact table with some junk dimensions, since both tables already have common dimensions.
ObjectiveC- Posts : 25
Join date : 2011-03-18
Re: datawarehouse modeling
Not really, and performance isn't the issue. The relationship between any two fact tables should always be assumed to be many-to-many. By aggregating each table along common dimensions reduces that relationship to one-to-one, which allows you to combine the two.
Alternately, you can union the two queries either before or after aggregation. This does the same thing, may perform a little better and avoids the need to do a full outer join.
Alternately, you can union the two queries either before or after aggregation. This does the same thing, may perform a little better and avoids the need to do a full outer join.
Similar topics
» DatawareHouse modeling (factless table)
» datawarehouse appliances
» It's only a Datawarehouse, How hard can it be
» Relational Datawarehouse
» DatawareHouse design - Suggestion req
» datawarehouse appliances
» It's only a Datawarehouse, How hard can it be
» Relational Datawarehouse
» DatawareHouse design - Suggestion req
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum