Forum Discussion
Native PowerBI data model vs SSAS Tabular: Change since new size limit announcement
Anonymous i think what you asking is a big question and difficult to answer as that solution requires pushing those skills to the self service users, so training and skill levels are vita, so its much bigger than just shifting technology, one needs to understand all the variables of your enviroment.
the best thing to do in my mind is to have a pilot group, do an end to end solution using this method and see what it brings up.
the benefit of a cube vs pulling those extracts from the data lake everytime is you have a built in layer that has already interpreted all the business rules, so to recreate that everytime you create a power bi model (unless you use that model as a source to other models, but scalability might be an issue).
what are the issues you are experincing with the current SSAS?
Hi,
Thank you for your input and sorry for my late reply.
Yes I know it is a big question :) I wouldn't say we have any issues with the current setup, I am more curious about if it is time to re-think the SSAS tabular models with the introduction of the 400GB native datamodels.
Right now we have dedicated IT resources who help us create tabular cubes according ot the business needs and requirements, but this is a long process. If we would use the native datamodels to become more self-serviced I completely agree that it would require pushing those skills onto the users, but here we would have a dedicated team on the business side who already are data champions and well connected with our data architecture. The benefit would be that we would much quicker be able to create new models and sources of analyses.
I guess what I am wondering is if there are some clear pros and cons with the two different setups from a technical perspective rather than the impact on knowledge and maintainability from a team/people/resource perspective. Makes sense?
Thanks again!
/Olof