Friday, August 16, 2013

Top-down or Bottom-up

Top-down or Bottom-up: - In chapter 2, we discussed the top-down and bottom-up approaches for building a data warehouse. The top-down approach is to start at the enterprise-wide data warehouse, although possibly build it iteratively. Then data from the overall large enterprise-wide data warehouse flows into departmental and subject data marts. On the other hand, the bottom-up approach is to start by building individual data marts, one by one. The conglomerate of these data marts will make up the enterprise data warehouse.

We looked at the pros and cons of the two methods. We also discussed a practical approach of going bottom-up, but making sure that the individual data marts are conformed to one another so that they can be viewed as a whole. For this practical approach to be successful. You have to first plan and define requirements at the overall corporate level. You have to weigh these options as they apply to your company. Do you have the large resources needed to build a corporate-wide data warehouse first and then deploy the individual data marls? This option may also take more time for implementation and delay the realization of potential benefits. But this option, by its inherent approach, will ensure a fully unified view of the corporate data.

It is possible that your company would be satisfied with quick deployment of a few data marts for specific reasons. At this time, it may be important to just quickly react to some market forces or ward off some fierce competitor. There may allot be time to build an overall data warehouse. Or, you may want to examine and adopt the practical approach of conformed data marts. 'Whatever approaches your company desires to adopt, scrutinize the options carefully and make the choice. Document the implications of the choice in the document.

No comments:

Post a Comment