Just as you are doing, it seems fine to me, although I always prefer to use "preceding load" statements, to distinguish every moment which fields come from the data base and which ones I'm actually loading into QlikView.
Concatenating both tables will append the contents of one to the other, so there will be no joins or data reduction, which may be useful for you. In your sample code, there's no need for label "Turnoverbloomberg:" as for all purposes, the result will be one table.
Hi what do you mean by preceding load statements? I thought I was loading everything from the database and everytime I need to refresh the table I need to reload the data from sequel server
Also after concatenating the table I need to formate the turnover date field
Is it correct to do this after the concatenation
Left(Monthname(Date(TURNOVER_DATE,'DD/MM/YYYY')),3) as TMONTH,
year(TURNOVER_DATE) as Tyear
ANGUYEN100 wrote:Hi what do you mean by preceding load statements? I thought I was loading everything from the database and everytime I need to refresh the table I need to reload the data from sequel server
It's just a suggestion, not a requirement. I mean your script should look something like
Table1:LOAD Field1, Field2;SQL SELECT Field1 Field2FROM Database;
ANGUYEN100 wrote:Is it correct to do this after the concatenation
There's no need to do a load resident since you can format your date fields in the load statement as
Table1:LOAD Field1, Field2, Date(DateField) AS DateField Month(Date(DateField)) AS Month, Year(Date(DateField)) AS Year;SQL SELECT Field1, Field2, DateFieldFROM Database;
You can create a master calendar which will likely help you in your chart design.
Hope that helps.
Wether you use preciding LOAD or not data will come but Qlikview's standard prefers
SQL SELECT *
This gives you flexibility to comment a field or uncomment it without changing sql statement. Also many transformation functions you can use in LOAD which database sql queries do not support.
Basically, LOAD is what you actually load into your application, while SQL is what you pull from your database. Think of them as an input (LOAD) and an output (SQL).
The "Preceding load" is _just_ a LOAD for the same fields you are pulling from your database, written by QlikView saving you time.