You are here: Commands > Join > Join Considerations

Join Considerations

To identify transactions for which no master table records exist, specify the transaction table as the primary table. And, to identify master records with no matching transactions, specify the master table as the primary table.

When using computationally intensive Analyzer functions to process fields in the secondary table (for example harmonizing key fields for a Join using the NORMALIZE() function), consider performing a field extract to extract all required secondary fields to a new secondary table prior to performing a Join. This will ensure a much more efficient Join because all computations in the computed fields will be resolved once as part of the field extraction rather than repeatedly as part of the Join.