Hi, all,
Thanks for your kind attention again.
I encountered a strange problem-whenever I process the cube(which is a small cube only, as I have already selected its partitions based on date dimension and the whole cube only with less than 1000 rows records), but I always got the problem which runs out the system drive space and of course resulted in the failure of the processing of the cube. I have actually manually allocated the storage locations which are not on the local system drive? Why did that problem happen and how can I figure it out?
That's really frustrated problem and please give me any advices and help on this if you have have any ideas what is going on for this.
I am looking forward to hearing from you and thanks a lot in advance again.
With best regards,
Yours sincerely,
What AS do you have AS2K or AS2K5?
Please, take attention to the queries that are send to data source sql server. I think you have somewhere cartesian product in your cube design that leads to the data explosion.
|||Hi,
Thanks for your kind attention.
I am running AS2005. Yes, I have found the cause of the problem, as the fact table where the measure group is from is too big with over million records, thus even though my cube has been partitioned with only less than 1 thousand records, as the processing always need to query into the whole fact table still which thus resulting in the running out of the system drive space (as I am doing some test with my virtual machine at the moment only, which only has a poor system drive storage.)
I have then particularly partiton the fact table with only a small proportion of data for the cube, and now the processing is ok then.
Thanks again.
With best regards,
Yours sincerely,
No comments:
Post a Comment