By default, AS2005 read the fact table without doing any join between this
table and related dimensions.
So by default AS2005 is "optimized", a step that you must manually do in
AS2000.
in AS2000 by default a query like select ... from table a inner join dimA
.... is executed.
So what's appends in your case, there is some keys in your fact table but
these keys doesn't exists in your dimension table. with AS2000, the inner
join will automatically exclude these rows in errors during the process.
Because AS2005 don't do this inner join, these missing keys raise an error.
there is many solutions:
first, validate your dimension to insure that these keys exists, if not
create these keys in your database. (most beautyfull solution)
you can also ignore any key error.
or you can tell AS2005 to automatically create an "unknown" member for your
missing keys. (new AS2005 feature)
[quoted text, click to view] "octoni" <octoni@discussions.microsoft.com> wrote in message
news:60D2BF3C-C34A-4BA6-A2CE-A3B705A99181@microsoft.com...
> Hi there, I try to migrate olap db to Analysis Services 2005, and error
> shows :
>
> Error Messages 6164
> Errors in the OLAP storage engine: The attribute key cannot be found:
> Table: dbo_Dim_Proper, Column: Kode_x0020_Proper, Value: 1632001. Errors
> in
> the OLAP storage engine: The record was skipped because the attribute key
> was
> not found. Attribute: Kode Proper attribute of Dimension: Dim_Proper from
> Database: BTN, Cube: PLM191, Measure Group: PLM191, Partition: PLM191,
> Record: 4.
> Errors in the OLAP storage engine: The attribute key cannot be found:
> Table: dbo_Dim_Proper, Column: Kode_x0020_Proper, Value: 1632001. Errors
> in
> the OLAP storage engine: The record was skipped because the attribute key
> was
> not found. Attribute: Kode Proper attribute of Dimension: Dim_Proper from
> Database: BTN, Cube: PLM191, Measure Group: PLM191, Partition: PLM191,
> Record: 7.
>
>
> Any idea ? Thanks!
>
> R'gards
> Octoni
