ssas dimension processing incremental

Question

I am having a large dimension and it is taking me more and more time to process it. I would like to decrease the processing time as much as possible

there is literally hundreds of different articles on how to process ssas objects as efficient and fast as possible. There are lots of tips and tricks that one can apply to speed up dimensions and cube processing. I managed to apply all or at least a big majority of them and I am still not happy with the result,.

I have a large dimension built on top of a table. It has around 60 mil records and it keeps on growing fast. It either add new rows to it or delete the existing ones. there are no updates possible

I am looking for a solution that will allow me to perform an incremental processing of my dimension. I know that the data in the previous month will not be changed. I would like to do smth similar to partitioning of my cube but on the dimension. I am using SLQ SERVER 2012 and to my knowledge dimension partitioning is not supported.

I am currently using process update on my dimension - I tried processing using by attribute and by table but both render almost the same result. I have hierarchies and relationships - some set to rigid. I am only using those attributes that are truly needed etc etc etc

process update has to read all the records in a dimension even those that i know have not changed. is there a way to partition a dimension? if I could tell SSAS to only process the last 3-4 weeks of data in my dimension and not touch the rest - it would greatly speed up my processing time.

I would appreciate your help

Answer 1

ok so I did a bit of research and I can confirm that incremental dimension processing is not supported. it is possible to do process add on a dimension but if you have records that got deleted or updated you cannot do that

it would be a useful thing to have but MS hasn't developed it and I don't think it will

incremental processing of any table is however possible in tabular cubes so if you have a similar requirement and your cube is not too complex then creating a tabular cube is the way to go