Deployment Failure Heirarchy

  • Working on analysis services tutorial where i am modifying measures and my heirarchy and this is my error message.

    Warning1Dimension [Date] : Avoid visible attribute hierarchies for attributes used as levels in user-defined hierarchies.00

    Warning2Dimension [Customer] : Avoid visible attribute hierarchies for attributes used as levels in user-defined hierarchies.00

    Warning3Dimension [Product] : Avoid visible attribute hierarchies for attributes used as levels in user-defined hierarchies.00

    Warning4Dimension [Product] : Define attribute relationships as 'Rigid' where appropriate.00

    Warning5Errors in the OLAP storage engine: A duplicate attribute key has been found when processing: Table: 'dbo_DimDate', Column: 'CalendarQuarter', Value: '4'. The attribute is 'Calendar Quarter'.00

    Error6Internal error: The operation terminated unsuccessfully.00

    Error7Server: The current operation was cancelled because another operation in the transaction failed.00

  • cook155 (4/20/2014)


    Working on analysis services tutorial where i am modifying measures and my heirarchy and this is my error message.

    Warning1Dimension [Date] : Avoid visible attribute hierarchies for attributes used as levels in user-defined hierarchies.00

    Warning2Dimension [Customer] : Avoid visible attribute hierarchies for attributes used as levels in user-defined hierarchies.00

    Warning3Dimension [Product] : Avoid visible attribute hierarchies for attributes used as levels in user-defined hierarchies.00

    Warning4Dimension [Product] : Define attribute relationships as 'Rigid' where appropriate.00

    Warning5Errors in the OLAP storage engine: A duplicate attribute key has been found when processing: Table: 'dbo_DimDate', Column: 'CalendarQuarter', Value: '4'. The attribute is 'Calendar Quarter'.00

    Error6Internal error: The operation terminated unsuccessfully.00

    Error7Server: The current operation was cancelled because another operation in the transaction failed.00

    The first thing I'd fix is the duplicate for #5 and see if that makes any of the other things go away.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • So to delete the duplicate i would just delete calendar quarter in the hierarchy?

  • So say that there is not a solution for this and i want to undo what i have done. There is not a way to get old saved back "not my recent". I just do not know how to get past this.

  • Jeff, Would that mean i made an extra attribute and need to delete it? How do i do that?

  • cook155 (4/21/2014)


    Jeff, Would that mean i made an extra attribute and need to delete it? How do i do that?

    I can't actually see your data so it would be up to you to do a little research on the underlying tables. Look at the fault for #5. You need to find that "duplicate". It may not actually be a duplicate... it could be keyed incorrectly or ???

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • cook155 (4/21/2014)


    Jeff, Would that mean i made an extra attribute and need to delete it? How do i do that?

    You don't need to delete any data. The 'duplicate' you are encountering is because your Calendar Quarter attribute likely uses only the CalendarQuarter column from your Date dimension as a Key column. Analysis Service doesn't know that Quarter 1 of 2013 is distinct from Quarter 1 of 2014, hence the error.

    What you need to do is define a composite key as the Key column for your Calendar Quarter attribute and, most commonly, the combination of Year and Quarter is used, e.g. 2013Q1 and 2014Q1. Now Analysis Services sees those as distinct values (as indeed they are of course) and your Dimension processing errors disappear (or at least that one does ;-)).

    Regards

    Lempster

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply