Data Mart Philosophical Design Differences
4 posters
Page 1 of 1
Data Mart Philosophical Design Differences
Hello,
I'm currently working on a project that entails developing a data mart to deliver logistics information
through SSAS cubes. My approach has been to first design a physical data mart
independent of the delivery mecahnism. SSAS cubes, SSRS reports, etc.,
will be used to deliver the data. The source system is a combination of OLTP and ODS
databases.
There's another school of thought at my current company: Rather than create a separate
physical data mart, create views over the current OLTP tables as a means of implementing
a "logical data mart", and deploying the SSAS cubes based on this logical view of a data mart.
Is this approach recognized by the Kimball Group?
I'm currently working on a project that entails developing a data mart to deliver logistics information
through SSAS cubes. My approach has been to first design a physical data mart
independent of the delivery mecahnism. SSAS cubes, SSRS reports, etc.,
will be used to deliver the data. The source system is a combination of OLTP and ODS
databases.
There's another school of thought at my current company: Rather than create a separate
physical data mart, create views over the current OLTP tables as a means of implementing
a "logical data mart", and deploying the SSAS cubes based on this logical view of a data mart.
Is this approach recognized by the Kimball Group?
dgorbea- Posts : 1
Join date : 2011-09-14
Re: Data Mart Philosophical Design Differences
I'm not sure you'll get a response from the Kimball Group. They frequent the boards infrequently. I'll put on my un-official Kimball cap though. Bad idea for all the reasons why data warehouses started in the first place.
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Re: Data Mart Philosophical Design Differences
Yep. It's been done before and the end result eventually turns into a major headache.
Re: Data Mart Philosophical Design Differences
I agree wholeheartedly with the previous two comments.
IMO it's a particularly bad idea when feeding SSAS cubes, as there are very limited options in that tool alone for handling dirty data. Once you start pointing it at live data, this leads to frequent processing failures which are difficult to debug.
I think a solid star schema is definitely a worthwhile investment for the architecture you described.
Good luck!
Mike
IMO it's a particularly bad idea when feeding SSAS cubes, as there are very limited options in that tool alone for handling dirty data. Once you start pointing it at live data, this leads to frequent processing failures which are difficult to debug.
I think a solid star schema is definitely a worthwhile investment for the architecture you described.
Good luck!
Mike
Similar topics
» Data mart design
» Data mart Design Question
» [b]Need Help on Employee Data Mart Design[/b]
» Foreign Key Constraints in Data Mart Design
» Human Resources Data Mart Design Guidelines
» Data mart Design Question
» [b]Need Help on Employee Data Mart Design[/b]
» Foreign Key Constraints in Data Mart Design
» Human Resources Data Mart Design Guidelines
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum