Question on large cube update processing

Hi, all experts,

Is there any way for us to process the updated cube partly ? In my case I only want to add KPIs to my cube which are related to a few measure groups. In this case, it seems like we have to process the whole partitions related to these measure groups which the new added KPIs are related to. But as to large cube with miliions of records, this could take a reasonable time. Therefore, I am wondering if there is any way that we are able to update and process only the new added properties such as these new added KPIs to the cube instead of having to process the large chunk of the cube data? I personally think it will be really great to have this feature.

Is there any way to achieve this in SQL Server 2005 Analysis Services? I am looking forward to hearing from you shortly and thanks a lot for your advices.

With best regards,

Yours sincerely,

Hi,

I think you just need to deploy your project.

Regards

|||

Hi,

Thanks. But as what I have always seen in my BIDS , whenever I deploy a project, the system process it first and then deploy it.

I am not quite sure what you really mean by deploy here if that is not the 'deploy' I understand.

Regards,

|||

Lucas is right, you just need to deploy without processing.

There is an option under the deployment settings of the project that sets whether the project is processed after it is deployed. I think the default setting is "Always Process", but you can change this to "Never" and the project will be deployed without initiating a processing operation.

For changes to things like the calc script and KPI's, you do not need to reprocess your data, deploying your changes is enough.

Question on cube processing and deployment

Hi, all experts here,

Thank you very much for your kind attention.

I encountered a very strange problem processing and deploying the cube to the analysis services server. The fact table where the measure group coming from only got several hundred rows, while at the same time I have other 6 dimensions with many attributes. My system drive currently still has nearly 1 GB space left, but when I deployed the cube, it took ages to run and ended up with process failure because of running out of space on my system drive.

This problem never happened before and it is really frustrated and I dont know what is going on.

Would please any experts here give me any advices. (I have tried ages, but still nothing really changes).

I am looking forward to hearing from you and thanks a lot in advance.

With best regards,

Yours sincerely,

Any expers know what is the cause of that problem?

Thanks.

With best regards,

Yours sincerely,

Question on attribute keys of measure group

Hi, dear friends,

I encountered a problem processing my cube with the error message telling: processing measure_group_name (which only has a count as its only measure)failed as attribute keys can not be found? Why is that? I have no idea why is that? Does it mean I have to include all the keys of the fact table where the measure group from in the measure groups as measures? Otherwise the system failed to identify the distinct count of the system? Or whatever measures the measure group contains, it alwys have to include all the keys including the dimension keys of dimensions which the measure group is related to?

Thanks in advance for your help and advices and I am always looking forward to hearing from you shortly from you.

With best regards,

Yours sincerely,

This message means that a column used to join the measure group to a dimension contains a value not found in the dimension. This is usually caused by a referential integrity error - the FK does not existing in the PK of the lookup table. However, it can also be caused by the presence of a null in the FK as by default this null will be converted to zero or blank which probably does not exist as a key in the dimension. You can handle the situation of nulls in FK columns within the fact table by setting the NullProcessing option in the advanced tab of the measure group relationship dialog from the Dimension Usage tab of the cube editor.|||

Hi, Matt,

Thanks a lot. Yes, the problem is the matching of the PK and the FK between the tables.

However, the data source view logical key and the relationships between tables are really annoying then, as it is not able to check the integrity of the tables?

With best regards,

Yours sincerely,

|||

So it sounds like you would like to have an option on the Data Source View to validate logical keys and relationships. I'd recommend you file a feature request on http://connect.microsoft.com/SQLServer/Feedback. Such feature requests will be automatically added to our issue tracking system for consideration in future releases and those that originate from a customer such as yourself get extra consideration since we know it's a real world scenario. If you can describe the scenario it will also help as it will allow us to better identify which requests will help the most people and how to implement them so that they actually provide the help intended.

Thanks, Matt

|||

Hi, Matt,

Thanks a lot and this sounds really a good idea of it.

With best regards,

Yours sincerely,