question

jgreer20092009 avatar image
jgreer20092009 asked

Should i create a named calculation in DSV or create member in MDX?

I have a cube with a value pre-calculated in the etl, that shows how many days a account is past due in the fact table. I need a way to either create a calculated member in MDX or create a named calculation in the dsv that will break down the days overdue as follows, and let me filter it in a cube. If it is between 1 and 29 days, then it is 'current'. IF it is 2o- 59 days, it is 'overdue', and so on. I am not sure the best way to do this. Any suggestions? Thank you!
sqlssasmdx
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
Pavel Pawlowski avatar image
Pavel Pawlowski answered
It depends on your overal design and how frequently you are updating the cube, but whenever possible, it is better to put the caluclation of attributes into the lower levels (DSV or even better into the ETL process itself). Once the attribute value is calculated in the loverl levers, than it's values are stored in the SSAS multidimensional model and SSAS will benefit from this (you can have aggregations defined for that attributes and also SSAS can build internal indexes to speedup filtering etc). If you calculate a value in MDX scrip and then would like to filter the data based on this calculated value, SSAS will not benefit from the above mentioned.
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.