Re: Help creating OLAP cube - attribute key cannot be found

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Hi,
thank you very much. Actually, the data and all its references EXIST in the
DB, which is what I checked for. I tried to use parts of the same "fact" in
different dimensions, which causes the error, because some records link to
the one, others to another dimension. Creating views, one for each dimension,
did the job.
Thanks,
rwh

"entaroadun" wrote:

What does the fact table look like? Are you sure that fact records
can join to every dimension view without dropping anything?

On Jan 9, 12:24 pm, rwh <r...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi,
I'm trying to build my first OLAP-Cube, but keep running into an error I
can't fix.
The data is based essentially on two tables, but unfortunately the different
dimensions and facts I want to base upon are differentiated only by a column
"itemType" in these tables. Sorry, this layout is a mess, but is caused by
reasons I can't control.
So, to get something more intuitive I've got a view for each itemType that
extracts the data from the tables like "SELECT * FROM tbl1 WHERE itemType=1".
All keys are defined as UniqueIdentifiers, a few 1-n and n-m relations exist
"logically", for each of them a view exists ("SELECT IDItem, IDParent FROM
tbl2 WHERE relationType=1"), constraints don't exist. In VS, I've build a
project, added the relations manually and created a cube using the wizard.
The dimensions seem to be correct, so I've successfully processed the
dimensions. Processing the cube gives the error: "attribute key cannot be
found" on a few lines. Setting the error-configuration to "Ignore errors
count" and each of the conditions to "Report and Continue" completes the
processing, but the log shows errors.

Everything I read about says, that this is by design and is related to
missing keys. Strangely, I don't find any key that is missing. However, some
of the views show the keys-GUID in upper-case, others in lower-case (but all
views have essentially the same layout). Applying LOWER(Key) doesn't help,
either.

Has anybody an idea, on how to determine which SQL-statements the processing
applies, so that I may find the reason why it doesn't find the keys or how to
solve this somehow?
BR,
rwh

P.S.:
SQL Server: 9.00.3054.00 SP2 Enterprise Edition
Visual Studio 2005:
Analysis Services: sorry, I didn't find a way to determine the version, the
Microsoft.AnalysisServices.AdomdClientUI.dll has version 9.0.3042.0
Office 2007
Windows Update doesn't find any updates needed, not even in Custom Mode.


.



Relevant Pages

  • Re: Help creating OLAP cube - attribute key cannot be found
    ... All keys are defined as UniqueIdentifiers, a few 1-n and n-m relations exist ... The dimensions seem to be correct, ... missing keys. ... Windows Update doesn't find any updates needed, ...
    (microsoft.public.sqlserver.olap)
  • Pivottable Filtering Bug crashes IE!!
    ... dimensions for a special substring. ... After that i set that keys to ... faulting module OWC10.dll, version 10.0.2621.0, fault ... Developer name the cause or even a solution for this ...
    (microsoft.public.office.developer.web.components)
  • Re: 800 Dimensions... Too many?
    ... My dimensions are all separate tables ... and my keys are all integers. ... this reduce the size of the cube and provides a better process performance. ... Please do not send email directly to this alias. ...
    (microsoft.public.sqlserver.olap)
  • Re: Many to Many to Many
    ... proliferation of dimensions quickly becomes unmanageable. ... pursuing a solution that combined 2 keys in a useful table, ... always be added/edited from the perspective of a spec/supplier instance. ... then it's the correct db design approach. ...
    (microsoft.public.access.tablesdbdesign)