Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
can we create new table in add load ?
or loading only new data from existing data ?
ADD can't create a new named table.
Edit: corrected. It seems that ADD can create a default table within qv.
Hi,
Add load is used to concatenate the data from one table to another table.
ADD can't create a new named table.
Edit: corrected. It seems that ADD can create a default table within qv.
Hi,
Simply put, this statement blindly appends data from one table to the data of another table, having similar signature, during partial reload. It does not check for any duplicate. Hence, ADD LOAD or ADD SELECT is usually follwed by distinct or a proper where clause.
e.g.
LOAD OrderID, OrderAmt from Order_May.csv;
ADD LOAD OrderID, OrderAmt from Order_June.csv;
This will simply concate data from Order_June to Order_May. But OrderID might be duplicated. Hence, this statement can be properly shaped to remove duplicate data as:
LOAD OrderID, OrderAmt from Order_May.csv;
ADD LOAD OrderID, OrderAmt from Order_June.csv Where Not Exists(OrderID);
For more details on load follow link below:
HTH,
Hirish
The add prefix can be added to any LOAD, SELECT or map...using statement in the script. It is only relevant during partial reloads.
Syntax:
Add [only] (loadstatement | selectstatement | mapstatement)
During a partial reload the QlikView table, for which a table name is generated by the add LOAD/addSELECT statement (provided such a table exists), will be appended with the result of the add LOAD/addSELECT statement. No check for duplicates is performed. Therefore, a statement using the add prefix will normally include either a distinct qualifier or a where clause guarding duplicates. The map...usingstatement causes mapping to take place also during partial script execution.
Arguments:
Argument | Description |
---|---|
only | An optional qualifier denoting that the statement should be disregarded during normal (non-partial) reloads. |
Example | Result |
---|---|
Tab1: LOAD Name, Number FROM Persons.csv; Add LOAD Name, Number FROM newPersons.csv; | During normal reload, data is loaded from Persons.csv and stored in theQlikView table Tab1. Data from NewPersons.csv is then concatenated to the same QlikView table. During partial reload, data is loaded from NewPersons.csv and appended to the QlikView table Tab1. No check for duplicates is made. |
Tab1: SQL SELECT Name, Number FROM Persons.csv; Add LOAD Name, Number FROM NewPersons.csv (txt) where not exists(Name); | A check for duplicates is made by means of looking if Name exists in the previously loaded table data (see the function exists under inter-record functions). During normal reload, data is loaded from Persons.csv and stored in theQlikView table Tab1. Data from NewPersons.csv is then concatenated to the same QlikView table. During partial reload, data is loaded from NewPersons.csv which is appended to the QlikView table Tab1. A check for duplicates is made by means of seeing if Name exists in the previously loaded table data. |
Tab1: LOAD Name, Number FROM Persons.csv; Add Only LOAD Name, Number FROM NewPersons.csv (txt) where not exists(Name); | During normal reload, data is loaded from Persons.csv and stored in theQlikView table Tab1. The statement loading NewPersons.csv is disregarded. During partial reload, data is loaded from NewPersons.csv which is appended to the QlikView table Tab1. A check for duplicates is made by means of seeing if Name exists in the previously loaded table data. |