leehbi (10/21/2016)
Thanks everyone for the excellent points.I'm thinking about this now as I manage a team of developers. I will definitely keep to DRY principles with the calculations at the lowest possible level. I know from experience that some things are more suitable to cubes/mdx but will keep these to the minimum. I will have to materialise aggregates in the DM as there are too many calculations for the MDX script IMO.
It's great we have so much choice 🙂
In terms of Excel calculations. The pace of change and flexibility analysts have with Excel is beyond that of the BI developers (day to day) but my view on this is to bring in logic into the DM that will benefit the wider corp level or save significant time. I think we have to do this otherwise the value of the DW will be eroded over time.
Thanks again.
I think of it as balance personally. Good balance does help the stack. I kind of given up trying to provide all the answers with the data. I just focus on the core ones and let the users help discover new ones. Then it's a decision on where it goes from there. That's the fun part! :hehe: