But that limitations are characteristics that must always consider:
• It has the Always use the Distinct keyword to create the link table. This is done so that we are only loading dimension fields in this table must not have duplicate records.
• If the key field is composed of several individual fields can be resource for the application. (In these cases, we can use the Autonumber ()
• The link table can become very large depending on the number of possible combinations that exist between or among the fields it's composed of.
• If the link table becomes immense, remember that QlikView needs to "walk" through the defined path between tables each time it needs to look for associations. An additional "hop" on this path, especially if it is through a large table, might slow calculation times for the end user.
