Forum Discussion
Which Join is the right one?
Hello Anonymous ,
the problem with the crossjoin-like behaviour is that your join fields don't create unique rows. So for each row in your table(s) there are multiple rows in the other tables (and in the same table itself). So with each join you are expontentially increasing rows.
Is it possible to create a unique row-identifier from the existing fields and join on them instead?
If not, the only option would be to match on the existing order of the row in the 3 tables itself. To use that you would have to add an index column to all your tables and join on them instead.
Community ChampionHello Anonymous ,
the problem with the crossjoin-like behaviour is that your join fields don't create unique rows. So for each row in your table(s) there are multiple rows in the other tables (and in the same table itself). So with each join you are expontentially increasing rows.
Is it possible to create a unique row-identifier from the existing fields and join on them instead?
If not, the only option would be to match on the existing order of the row in the 3 tables itself. To use that you would have to add an index column to all your tables and join on them instead.