Problem processing new cube

All,
When I try to "Design Storage" for a new cube, I get
a "Fact table size can not be 0" message. (I am in the
Cube Editor...) If I focus on the fact table and
select "Browse Data", the data is displayed as it should
be. So, the fact table size clearly is not "0".
From Query Analyzer, I can select rows. The table has over
one million rows in it.
I can't see anything obvious, such as "Refresh connection"
that would seemingly rectify this problem.
Any help appreciated.
TIA,
MikeIn the cube editor, set a value for the Fact Table Size property in the
Advanced tab of the property panel. This value along with the sizes of
dimensions is used during the aggregation design process.
- Matt Carroll
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:013901c3c58c$86ab1c40$a301280a@.phx.gbl...

quote:

---

> All,
> When I try to "Design Storage" for a new cube, I get
> a "Fact table size can not be 0" message. (I am in the
> Cube Editor...) If I focus on the fact table and
> select "Browse Data", the data is displayed as it should
> be. So, the fact table size clearly is not "0".
> From Query Analyzer, I can select rows. The table has over
> one million rows in it.
> I can't see anything obvious, such as "Refresh connection"
> that would seemingly rectify this problem.
> Any help appreciated.
> TIA,
> Mike

---

Problem processing cube

I am getting the error:

Warning 2 Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: B@. - key@. of Dimension: Brcledger from Database: Misys, Cube: Misys 1, Measure Group: Brcledger, Partition: Brcledger, Record: 24163. 0 0

I have read that this is caused by a referential integrity problem however, the fact table is the dimension table, and the joint primary key is definitely unique. There doesn't seem to be anything special about record number 24163 So why can i not process my cube?

Martin

Just incase it is any help.. the other error message which comes up I have pasted here:

Warning 1 Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_brcledger, Column: B_x0040_, Value: 0; Table: dbo_brcledger, Column: key_x0040_, Value: 474142463032485130310000000C. 0 0

SELECT *
FROM brcledger
WHERE (key@. = '474142463032485130310000000C')

Returns 1 result

|||

You have a situation when Analysis Server cannot find a key in the dimension while processing partition.

I would guess you might have problems with dimension process that lead to partition processing errors.

Try re-process your Brcledger dimension change processing options to report and stop on every error.

After you fix dimension problems you should be able to process your partitions without a problem.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

I have the same problem but it only occurs when i define my dimension as a time dimension. ]

Also my fact table is a view which gets it's surrgate keys by joining to the dimension tables in its definiton. This might be connected but the cube processes fine with the same data source, fact table, dimensions etc as long as i dont define the dimension as a time dimension.

Also the value of the attribute keys it cant find is always zero '0'. There are the same number of errors in the processing as there are nulls in the key column of the fact table. So i assume the nulls are being converted to 0 and then the referential integrity goes.....

Please help,

thanks,