trying to optimise FoodMart 2000, but failing.

  • If you want to try to optimise the schema with the time dimension in FoodMart 2000, why is it not possible?

    The lowest member is Month, so setting the memberkey column to "time_by_day"."time_id" and member keys unique to true should be a decent first step, but then I get the following message:

    Analysis Server Error: Detected two sibling members with the same name: 1 (Month).; Time:21/06/2002 15:35:01

    Question is - Why?

    Paul Ibison

    Paul.Ibison@blueyonder.co.uk


    Paul Ibison
    Paul.Ibison@replicationanswers.com

  • If you set the member key to time_id but do not change the member name column (also to time_id) you will create a situation where multiple members of the same parent have the same name - this is not allowed and results in the 'duplicate member' error you are receiving.

    If you consider this for a moment, you'll see why: since the grain of time is day, many time rows (with unique time_id values) have the same Month value.

    Scot Reagin

    sreagin@aspirity.com

    Scot J Reagin

    sreagin@aspirity.com

    Scot J Reagin
    sreagin@hitachiconsulting.com

Viewing 2 posts - 1 through 1 (of 1 total)

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