Please help me, we are currently doing Data Modelling in a SSAS Cube and share the data to the user, but my new boss doesn't know or trust DAX and relationship (doesn't understand it) so he wants to make a huge flat table with everything in it. Help me find arguments against that.

​

Basically, if we go full flat table, I will lose the ability to use Power BI, use DAX, or create model as an analyst. I will basically become a excel monkey doing SumIfs and Index/Match in excel on a huge flat table. (he doesn't want me to upload the flat table in power query to I can normalized it and do a model either as he wants to be able to do F2 and see the formula (cant do that with DAX)

​

This also isn't just for me, but for the whole organization. So I will try to do a power point showing:

​

-a centralized SSAS Cube in Visual Studio deployed to every user (I offer to move to IT, to build and maintain and test and deploy the model)

VS

-a flat huge table in SQL that user will import in Excel and do SumIfs and Index/Match on it.

Please help me find argument to put in the power point (pros/cons) as I am no export.

Thank you,

​

EDIT:

I found this in Chapter 10 of The Excel User's Guide to DAX by Rob Collie & Avie Singh:

https://i.imgur.com/skIK9nl.png

But they do not mention the "many advantages" they just tell you there is many, can anyone let me know what are those "many advantages" ?