Forum Discussion

brunozanoelo's avatar
brunozanoelo
Post Patron
9 years ago
Solved

Compound key

Why i cant use Compound Key in the binding of the tables?

Case:
Company 1 Seller 5
Company 1 Seller 6

Company 2 Seller 5

Should o use one column like "First Pk"_"Second Pk"?

1_5
1_6
2_5

Thanks... waiting for a reply.

Need Help
Show and Tell
Tutorial Requests
  • Phil_Seamark's avatar
    Phil_Seamark
    9 years ago

    Hi brunozanoelo ,

     

    Compound keys are less essential in an Analytics/Reporting environment, but yes if you concatenate the values you can create relationships between tables.

4 Replies

  • Phil_Seamark's avatar
    Phil_Seamark
    Microsoft Employee
    9 years ago

    Hi brunozanoelo ,

     

    Compound keys are less essential in an Analytics/Reporting environment, but yes if you concatenate the values you can create relationships between tables.

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      Hey Phil_Seamark,

       

      I think you need to do some clarification here. On what regards do you claim that compound keys are less essential? Why duplicate data which degrade performance??

    • MaxW's avatar
      MaxW
      Advocate II
      8 years ago

      Please be careful concatenating values to create compound keys, ideally convert id's to text and use a separator between them. This is a potential performance hit (text lookups are much slower than integer), but it is often necessary to avoid duplicate keys.

       

      Consider:

      Company 1 employee 12  key=112  

      Company 11 employee 2  key=112