title: Analysis Services Dimension - Key column usage where two attributes are at the same level
body: <p>My query is regarding the setting of the KeyColumn property of a dimension attribute in analysis services (2008). Specifically it boils down to: I have a dimension, there are three attributes which I am currently concerned with: SudoKey, Code and Description.</p>
  
  <p>SudoKey is the most granular, but Code and Description are at the same level, that is to say for every Code member, there is one Description member, and vice versa.</p>
  
  <p>My users want to have access to both individually (some users find codes more efficient, whereas others prefer to work with the descriptions).</p>
  
  <p>I am currently thinking that for efficiency rather than define SudoKey > Code <em>and</em> SudoKey > Description relationships, I should be defining a SudoKey > Code relationship and using Code as the KeyColumn value for Description (with Description for the NameColumn value)... Only I am not confident about what I am doing and success is critical!</p>
  
  <p>Any input would be much appreciated! :)</p>
  
  <p>Edit: What I mean to say is, I don't know if this will work/if it will have the intended effect of reducing the work which Analysis Services has to do.</p>