WhereScape have added some new functionality into WhereScape RED version 5.6.4 that improves how dimensions are optimized within Analysis Services 2005. Attribute relationships are now automatically defined by WhereScape RED when creating a cube, which will improve the top end aggregation performance. These attribute relationships are exposed and managed within WhereScape RED through the use of member properties (a right click option on a cube). The two types of attribute relationship (rigid and flexible) are supported.
When creating a cube using version 5.6.4+ the cube dimensions may look different if a level within a hierarchy is not using a key and / or is not unique. This is because the attribute relationship is only built between two levels of a hierarchy, rather than all the way up from the leaf member. For example if you have a hierarchy of country -< city, where you can have the same city name in multiple countries you must ensure that the city key column is unique otherwise all data against that city name will be allocated to just one of those countries. An artificial key can be built (if one is not available) by creating an additional column in the dimension that is populated with the country_code concatenated to the city_code thereby ensuring all city keys are unique.
If the new hierarchy structure does not fit with your requirements and you preferred the non-optimised view of the dimension then you can delete the attribute relationships in WhereScape RED by deleting the member properties defined on the cube in WhereScape RED. This will create a cube identical in structure to those cubes created in prior versions of WhereScape RED.