modeling corportae data sources

[nfldbunker]

hi everyone


just a quick question.we had an outside our organization  consultant in and build a reporting model and a couple of cube feeds from frameowkr manager.he suggested connecting all data sources to the one model and build one giant complex system. This seems a bit odd and comlex and massive in scope.

I feel build many models and reporting environments joining certain data sources when required.

what is some other views and thoughts on this view?

Any best practise documents or other articles that anyone would suggest

please let me know

bunker

[MFGF]

Hi,

The benefit of building a single model and publishing targeted packages from this is that you only model each aspect of your data once, and can then potentially reuse this in many packages.  This guarantees conformity across the business, and save you lots of work too.

Imagine you had thirty different FM projects for the business, and the way your business describes products then changes.  You would need to figure out which are the models that describe products and then make the same change in each one, which would be time-consuming and risky (you would need to ensure you make exactly the same change, and that you hadn't missed changing any of the models).

MF.

[mgibson]

I disagree with that consultant's recommendation.  What he suggests sounds like an extremely complex and high-maintenance task, with probably little benefit.

The only reason I can see why this should be done is to consolidate data from different sources into the one report, etc.

However, if you do genuinely need to create reporting with data from different data sources then you should investigate using multi-tab dashboards, etc.

Don't do it!

Mick