Forum Discussion
Report Storage Mode when using ADDCOLUMNS Dax?
Yes, If you've created a calculated table using DAX you've effectively created a composite model and this new table in using in-memory storage and will need to be refreshed on a schedule in order to pick up any new data.
Super UserYes, If you've created a calculated table using DAX you've effectively created a composite model and this new table in using in-memory storage and will need to be refreshed on a schedule in order to pick up any new data.
Thanks for the reply. So if i use New Table option that will turn the direct query report to composite model?
- d_gosbell
That is correct, because the calculated table feature creates an in-memory table. If you don't want a composite model you would have to either look at trying to add a calculated column to your direct query table, those are supported now provided you only do calculations on a row by row bases (so you can't calculated ratios or rankings that require comparing data in the current row to other rows in the table). Or you could look at pushing the logic down to a SQL view, maybe trying to use an indexed view if performance becomes an issue.
Thanks for the explanation. Yes performance has become an issue in my report. I would consider doing the calculations in the SQL query itself.
Regards,
Maddy