I get a each city in every state, when the city does not exists for the state in my loaction dimension

Answered I get a each city in every state, when the city does not exists for the state in my loaction dimension

  • Friday, March 01, 2013 4:56 PM
     
     

    So we have a large data extract for service tickets (help desk tickets).  Each row in the extract has data for a ticket including the ticket info, customer info and analyst info.  I used the extract to populate a star schema, so I have factTicket, DimTicket, DimCustomer, DimAnalyst and DimDate.  I used the ticket number as the the primary and foergn keys in all my tables.  Not sure if using this as Key was best idea, but I am newbie to this.

    I created a AnalystLocation ( State, City, Location) and linked it to the Analyst dimension.  In the dim I created one heirarchy.  I defined Key columns for city(state,city) and location(state, city, loaction) and set the name columns.  I defined my attribute relationships (Key > loaction > City > State) with rigid relationships.  I used the Add Business Inteligence wizard to define Georgraphy type dimension where City = Analyst City, Building = Analyst location and State or Province = Analyst State.

    When I browse the dimension I am getting each city in every state, i.e. I get Portland in every state, I get Anchorage in every state.

    Does anyone one see what I am missing or where my mistake is? 

    Any help is appreciated.

All Replies

  • Tuesday, March 05, 2013 2:53 AM
    Moderator
     
     Answered

    I created a AnalystLocation ( State, City, Location) and linked it to the Analyst dimension.  In the dim I created one heirarchy.  I defined Key columns for city(state,city) and location(state, city, loaction) and set the name columns.  I defined my attribute relationships (Key > loaction > City > State) with rigid relationships.  I used the Add Business Inteligence wizard to define Georgraphy type dimension where City = Analyst City, Building = Analyst location and State or Province = Analyst State.

    Hi Computermike,

    It seems that this issue might be caused that the incorrect key columns for City attribute. In this case, please try to define a collection key for the key column of county attribute. In addition, I recommend you take a look at Adventure Works cube sample how to create the geography dimension.

    We can find the Adventure Works sample in the following path:
    Drive:\Program Files\Microsoft SQL Server\100\Tools\Samples

    If you have any feedback on our support, please click here.

    Regards,


    Elvis Long
    TechNet Community Support