Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSAS 2008 Unknown Member Expand / Collapse
Author
Message
Posted Friday, February 12, 2010 4:00 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, March 31, 2014 10:22 AM
Points: 4, Visits: 31
I'm using SSAS 2008. I have a fact table that could contain NULL values that are associated with a dimension. Instead of ignoring dimension errors, I set the Unknown Member attribute in the dimension to visible. My understanding is that after setting that attribute, during cube processing, if a null is encountered no error is thrown, but rather that fact is thrown in the unknown bucket for that dimension.

I am still getting the dimension error :
Errors in the OLAP storage engine: The attribute key was converted to an unknown member because the attribute key was not found. Attribute Branch Id of Dimension: Lending Branch from Database: Rapid2, Cube: Rapid2Cube, Measure Group: Request Queue Trans Query, Partition: Request Queue Trans Query, Record: 1.

Am I missing something?

Thanks for the help, in advance :)
Post #865001
Posted Tuesday, February 23, 2010 4:19 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: 2 days ago @ 12:52 PM
Points: 13,636, Visits: 11,509
I think the problem lies in the fact that when the cube is processing your fact table, he will link the surrogate keys (or attribute key, whatever you use) to your dimension. If the SK is null he can not map the relationship.

For example:

FACTS (SK_Customer, amount, date_transaction)
1 500 2010/02/23
null 600 2010/02/23
2 1000 2010/02/22
...

CUSTOMER DIMENSION (SK_Customer, customer_ID, first_name, last_name)
1 customer1 firstname1 lastname2
2 customer2 firstname2 lastname2
...

In this case, the surrogate key of the second fact is missing. During processing, the cube can not find the SK with the value 'null' in your dimension, causing an error. Therefore you should map the null values in your fact table to surrogate key -1 and insert the following line in your dimension (following the previous example):

-1 N/A NOT APPLICABLE NOT APPLICABLE (N/A for codes, NOT APPLICABLE for text items)

Now the cube will find the NOT APPLICABLE member instead of nothing and therefore there is no error.

Anologue you can use a SK with value 0 for UNKNOWN members (and thus creating your own unknown member).

You can do this mapping in the ETL fase or in the DSV.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #871031
Posted Sunday, September 25, 2011 10:48 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, December 15, 2014 3:09 AM
Points: 1,046, Visits: 1,846
Perfect explanation by the Koen. Just to add my two cents...

Make an effort to assign some default values to such dimension entities.


Regards/Raunak
Now a member of Linkedin

Please visit the all new Performance Point Forum
Please visit the all new Data Mining and Business Analytics Forum
Post #1180721
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse