QlikView Reference Manual.pdf - QlikCommunity - QlikView

load * from file2.csv;
.. .. ..
join (tab1) load * from file3.csv;
Back to Script Statements and Keywords (page 219).
Keep
The keep prefix between two Load (page 246) or Select (SQL) (page 262) statements has the effect of reducing
one or both of the two tables before they are stored in QlikView, based on the intersection of table data.
The keep keyword must always be preceded by one of the prefixes Inner (page 239), Left (page 244) or
Right (page 259). The selection of records from the tables is made in the same way as in a corresponding
join. However, the two tables are not joined and will be stored in QlikView as two separately named tables.
Note!
The explicit Join (page 243) keyword in QlikView script language performs a full join of the two tables.
The result is one table. In many cases such joins will result in very large tables. One of the main features of
QlikView is its ability to make associations between tables instead of joining them, which greatly reduces
memory usage, increases processing speed and offers enormous flexibility. Explicit joins should therefore be
generally avoided in QlikView scripts. The keep functionality was designed to reduce the number of cases
where explicit joins needs to be used.
Back to Script Statements and Keywords (page 219).
Left
The Join (page 243) and Keep (page 244) prefixes can be preceded by the prefix left.
If used before join it specifies that a left join should be used. The resulting table will only contain combinations
of field values from the raw data tables with a full set of data from the first table.
If used before keep, it specifies that the second raw data table should be reduced to its common intersection
with the first table, before being stored in QlikView.
left( join | keep) [ (tablename ) ](loadstatement |selectstatement
)
Examples:
Table1
A B
1 aa
2 cc
3 ee
Table2
244
A C