Forum Discussion
Row or Column for performance and usability
Hello, I have a report already built for which I am trying to look into performance improvement. I have a simple star schema and my fact table is originall in row storage. Month Market ...
Anonymous as a best practice you always want to keep your data unpivoted and there are many reasons:
- you can filter on any of the attributes (measure in your case)
- you need only one measure and use the attribute column on column well of the matrix visual, or can be used on legends in other visuals.
- ability for drill through on attribute
- custom tooltip pages will be easy to build
There are may more reasons but the above list is a good starting point.
but doesnt this limit the ability to create calculated columns and makes DAX more complex if I am using more than one of the measures in these calculatations.
For example instead of doing SUM(TABLE[Sales]) I will need to do CALCULATE(Sum(TABLE[Value], TABLE[Measure] = "Sales")