Showing posts with label Data Mart Design. Show all posts
Showing posts with label Data Mart Design. Show all posts

Thursday, May 23, 2013

[SQL Server Data Warehousing] Data Mart Design -Help


Data Mart Design -Help



Hello,


I have a requirement where I need to build a data mart for consumer who have been contacted -for visiting our website and showing interest in our products. On Daily basis the Marketing Team contacts potential customers. The campaign management tool currently logs consumers who have been contacted on daily basis in a table ( currently approx 200m ). For Analysis purposes I need to create a DM . While Designing Fact Table I was thinking since many rows are logged on a daily basis I would need to create Fact tables based on a year - e.g FactTable2009, FactTable2010, FactTable2011, FactTable2012 and so on..


  • Is it a good idea to create separate Fact Tables for each year? ( Since lot of data volume is expected in an year)

  • There would be around 10-11 dimensions/lookup tables

  • The Analysis would comprise of Customer retention and responsiveness of the Email Campaigns. 

Please advice...What would be the best design approach in this situation.


 Thanks,



EVA05



.

social.technet.microsoft.com/Forums

Monday, May 20, 2013

[SQL Server Data Warehousing] Data Mart Design -Help


Hello,


I have a requirement where I need to build a data mart for consumer who have been contacted -for visiting our website and showing interest in our products. On Daily basis the Marketing Team contacts potential customers. The campaign management tool currently logs consumers who have been contacted on daily basis in a table ( currently approx 200m ). For Analysis purposes I need to create a DM . While Designing Fact Table I was thinking since many rows are logged on a daily basis I would need to create Fact tables based on a year - e.g FactTable2009, FactTable2010, FactTable2011, FactTable2012 and so on..


  • Is it a good idea to create separate Fact Tables for each year? ( Since lot of data volume is expected in an year)

  • There would be around 10-11 dimensions/lookup tables

  • The Analysis would comprise of Customer retention and responsiveness of the Email Campaigns. 

Please advice...What would be the best design approach in this situation.


 Thanks,



EVA05



.

social.technet.microsoft.com/Forums

Friday, May 17, 2013

[SQL Server Data Warehousing] Data Mart Design -Help


Hello,


I have a requirement where I need to build a data mart for consumer who have been contacted -for visiting our website and showing interest in our products. On Daily basis the Marketing Team contacts potential customers. The campaign management tool currently logs consumers who have been contacted on daily basis in a table ( currently approx 200m ). For Analysis purposes I need to create a DM . While Designing Fact Table I was thinking since many rows are logged on a daily basis I would need to create Fact tables based on a year - e.g FactTable2009, FactTable2010, FactTable2011, FactTable2012 and so on..


  • Is it a good idea to create separate Fact Tables for each year? ( Since lot of data volume is expected in an year)

  • There would be around 10-11 dimensions/lookup tables

  • The Analysis would comprise of Customer retention and responsiveness of the Email Campaigns. 

Please advice...What would be the best design approach in this situation.


 Thanks,



EVA05



.

social.technet.microsoft.com/Forums

Tuesday, May 14, 2013

[SQL Server Data Warehousing] Data Mart Design -Help


Hello,


I have a requirement where I need to build a data mart for consumer who have been contacted -for visiting our website and showing interest in our products. On Daily basis the Marketing Team contacts potential customers. The campaign management tool currently logs consumers who have been contacted on daily basis in a table ( currently approx 200m ). For Analysis purposes I need to create a DM . While Designing Fact Table I was thinking since many rows are logged on a daily basis I would need to create Fact tables based on a year - e.g FactTable2009, FactTable2010, FactTable2011, FactTable2012 and so on..


  • Is it a good idea to create separate Fact Tables for each year? ( Since lot of data volume is expected in an year)

  • There would be around 10-11 dimensions/lookup tables

  • The Analysis would comprise of Customer retention and responsiveness of the Email Campaigns. 

Please advice...What would be the best design approach in this situation.


 Thanks,



EVA05



.

social.technet.microsoft.com/Forums

Search This Blog