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,