MSBI - Business Intelligence

which model should you use, Multidimensional vs Tabular? Well, there is no clear-cut answer, but there are some factors that can make you choose one over the other: If you want to use DAX, you have to use Tabular If you want to use Power View, you have to use Tabular If your dataset is extremely large, go with Multidimensional If you need writeback support, you have to use Multidimensional If you need access to many different external data sources, choose Tabular If you need complex calculations, scoping, and named sets, choose Multidimensional If you need extreme speed and consistently fast query time, choose Tabular If you need Many-to-Many relationships, choose Multidimensional (can be done in Tabular but difficult) If your solution requires complex modeling, choose Multidimensional If you need any of the following features, you must use Multidimensional: Actions, Custom Assemblies, Custom Rollups, Custom Drillthrough Actions (but BIDS Helper adds support for action...

Why Tabular? SQL Server Analysis Services is a solid and mature platform that now serves as the foundation for two different implementations.  Multidimensional models are especially suited for large volumes of dimensionally-structured data that have additive measure values that sum-up along related dimensional attributes & hierarchies.   By design, tabular architecture is more flexible than multidimensional in a number of scenarios.  Tabular also works well with dimensional data structures but also works well in cases where the structure of the data doesn’t resemble a traditional star or snowflake of fact and dimension tables.  When I started using PowerPivot and tabular SSAS projects, I insisted on transforming data into star schemas like I’ve always done before building a cube.  In many cases, I still do because it’s easier to design a predictable model that performs well and is easy for users to navigate.  A dimensional model has order and...