Dimensional Modelling : Online Media Ads Company
2 posters
Page 1 of 1
Dimensional Modelling : Online Media Ads Company
Hi
I am designing a Dimensional Model for a company which provides ads to website.
they track the ad performance and load the log files into 3 different tables.
e.g. Impressions log, Click log and Event Log
now these table are pretty huge and we are trying to deign a datawarehouse which would help them to slice and dice data in all manner and also give good performance.
The problem is that we need to have grain at click,impression and event level which makes fact table very huge.
If anybody has faced similar situation she/he can give me a pointers for above situation
What are the best strategies to be followed in such a case while designing DW schema.
This is my first DW project
I am designing a Dimensional Model for a company which provides ads to website.
they track the ad performance and load the log files into 3 different tables.
e.g. Impressions log, Click log and Event Log
now these table are pretty huge and we are trying to deign a datawarehouse which would help them to slice and dice data in all manner and also give good performance.
The problem is that we need to have grain at click,impression and event level which makes fact table very huge.
If anybody has faced similar situation she/he can give me a pointers for above situation
What are the best strategies to be followed in such a case while designing DW schema.
This is my first DW project
Re: Dimensional Modelling : Online Media Ads Company
I've done clickstream before. The modeling itself is pretty straight forward. There is typically a user and a session cookie that helps identify basic contexts. Loads are fairly simple since facts are not updated. Stick to a clean dimensional model and pick the right platform to host the data.
Re: Dimensional Modelling : Online Media Ads Company
Thanks for inputs.
After going through current log table structure.
I could see there are three fact table to be developed.
1. event
2. Click
3. Impression
Event - open page, go to a page etc.
Impression : ad is shown to user
click after seeing ads and he clicks on impression
and since these things will not happen at a time. its good to have three different fact table.
Please comment on my understanding.
Also, how do you guyes tackle Unique Users measure in such a model. as it can not be aggrgated and having Fact table at lowest granularity will raise a performance flag.
After going through current log table structure.
I could see there are three fact table to be developed.
1. event
2. Click
3. Impression
Event - open page, go to a page etc.
Impression : ad is shown to user
click after seeing ads and he clicks on impression
and since these things will not happen at a time. its good to have three different fact table.
Please comment on my understanding.
Also, how do you guyes tackle Unique Users measure in such a model. as it can not be aggrgated and having Fact table at lowest granularity will raise a performance flag.
Similar topics
» Dimensional Model for Online Job Portal
» Dimensional Modelling compared to Relational (3NF +) Modelling for DSS
» Dimensional modelling
» Dimensional Modelling
» Start of Dimensional Modelling
» Dimensional Modelling compared to Relational (3NF +) Modelling for DSS
» Dimensional modelling
» Dimensional Modelling
» Start of Dimensional Modelling
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum