CODEWITHSUNDEEP
modelingssas-tabularazure-analysis-services
SniperPro
SniperPro

Reputation: 105

Modeling Analysis service tabular fact with many columns

I have a tabular analysis service fact table with more than 150 attributes (degenrate) and measures (Invoice fact table).

I would like to improve the user experience when browsing the table on azure AS. Is it a good idea to split the table horizontally to 3 tables each table contains a set of columns and measures (the number of rows remains the same on 3 tables) ?

Upvotes: 0

Views: 44

Answers (1)

TheRizza
TheRizza

Reputation: 2062

I don't change a model for browsing's sake. Browsing is a reporting issue. Modeling is modeling. Build a good dimensional model in a star schema. Big wide tables are bad.

I would look for anything that ought to be a dimension to pull out, and build some junk dimensions, and for sure I would move the measures to a DAX table. But if whatever is left is ugly, then I would just leave it and build a report for browsing.

Upvotes: 0

Related Questions