One App for five reports VS Five apps for five reports

[bing_jville]

Hi guys

I have five big financial reports to build. They use the same database, but involving different fact tables, and each has its own dim table sets (e.g. I have to load dim customer 3 times).  And some reports are aggregated, some reports are not.

So I have to make a decision on:

1. Build a full data model includes every table I need for the five reports. It will be a combination of dim tables, inner join, mapping table. So I have a nice and clean model for this subject area.

2. Build one app for each report, with minimal tables loaded. Like building a SSRS report. So the report runs nice and fast. They won't affect each other.

Any thoughts? 

Thank you.

[JordyWegman]

Hi Bing,

My advice would be to go for the second option. This is not only for the developer easier, read you, but also better for the end user experience for the speed of the application. Also, when something fails, you maybe still have 4 working reports, instead of all 5 that are down.

Jordy

Climber

[bing_jville]

Thanks Jordy.