Time Dimension error
Hi,
I've created a cube and now i'm trying a add a time dimension, it gives me an error. the time dimension i've created is using server time dimensions which has year, quarter, month and date attributes, when browse the dimension it looks fine but i'm trying to add this to cube and try to process cube it give a me this error
Warning 1 Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Ticket, Column: SalesDateTime, Value: 9/21/2004 4:29:53 PM. 0 0
Error 3 Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. 0 0
I set relationship type to regular and mapped the date from time dimension to a dattime field in fact table
thanks
-Guri
[828 byte] By [
Guri] at [2008-2-20]
Hi All,
Any answer to the above question? We too are suffering from a similar error.
If you've got an answer, kindly post it on this website at the earliest
Thanks,
irfan
I don't have an answer but I do have a question.
I have been trying to create a time dimension. When I select years and give it the column, that column disappears and I cannot add quarter, month, etc. The docs say that there are check boxes to use but I have no check boxes.
How did you get yours to work?
Thanks,
Roy
I get the same error - attribute key can't be found - I'm using the time dimension built without using a datasource - but using the template that comes with SSAS 2005 - all PK_Date values are by day, at 12:00:00 AM - Is there a way to change how the relationships between date fields relate to this dimension?
Is there a significance with respect to using smalldatetimes and datetimes?
I think you cann't have time stamp in datetime field in Fact table, the value should look something like this "2005/1/1 12:00:00" (time is always 12:00 AM), if there are different time then the key don't match
Believe it or not, I get around this by converting the date time value in the fact table to an nvarchar = YYYY-MM-DD
and that works.
STUPID in the extreme to have to do that, but it works.
Related issue I have is that converting back to a datetime (after removing the time portion) seems to cause null values in the fact table relationship to be converted to '12:00 A.M.' which then fails to match the dimension.
The values in the query inside Analysis services are still NULL, so it must be during the actual processing of the cube
