Qlik Community

QlikView Scripting

Discussion Board for collaboration on QlikView Scripting.

Announcements
QlikView Fans! We’d love to hear from you.
Share your QlikView feedback with the product team… Click here to participate in our 5-minute survey.
Rules, plus terms and conditions, can be found here.
Not applicable

Joining/Keeping after inner join..help needed

Hello,

I have table C in which i am inner joining two tables A and B. Then there is another table D where i am aggregating some fields from table C..

C:

load ......

resident A

;

inner join (C)

load ......

resident B;

D:

load ......

Max(..)

resident C

group by .....

;

Now the problem is that after C table has been loaded, It takes a lot of time to load table D. When i looked into the log i found that after table C has been loaded, there is a statement Joining/Keeping after which table D starts loading. However, I would not want this table D to be joined to anything. I am just loading data from the previous table C. Can someone help please

Arif

4 Replies
brenner_martina
Valued Contributor II

Joining/Keeping after inner join..help needed

Hi Arif,

you have to rename all fields in your Table D. QlikView joins all fields with the same name.

Greetings from Munich

Not applicable

Joining/Keeping after inner join..help needed

Hello,

Thanks for the response. I have qualified all the names in table D..so that should be out of question

Arif

brenner_martina
Valued Contributor II

Joining/Keeping after inner join..help needed

Hi, Arif,

how long did you wait for loading Table D and how many data are loaded in Table C? Because Group By really needs a lot of time without showing the time.

Not applicable

Re: Joining/Keeping after inner join..help needed

Hello ,


Thanks for your response. Actually the scenario is now as below, and now i am getting the table not found error..I am using some base tables and then some derived tables. in the last inner join, i get the error that table not found even though the table has been successfully create, which i can verify from the logfile too. As I have identified below, the error occurs only in the last statement. I have also tried to qualify the tables after calandar table so that each table has a different name but then it gives out of memory error. Can you please help

Planning_View:
LOAD PLAN_WEEK as PV_PLAN_WEEK,
     ITEM_CODE AS PV_MM_ITEM_CODE,
     FORE_WEEK as PV_FORE_WEEK, 
     ITEMDEMAND
     FROM

(txt, codepage is 1252, embedded labels, delimiter is '\t', msq);

Calandar:
LOAD PERIOD ,
WEEK
FROM

(txt, codepage is 1252, embedded labels, delimiter is '\t', msq);

Plan_Calandar:
LOAD PERIOD AS PV_PLAN_PERIOD,
  WEEK AS PV_PLAN_WEEK
RESIDENT Calandar;
INNER JOIN (Plan_Calandar)
LOAD PV_PLAN_WEEK
RESIDENT Planning_View;
 
Fore_Calandar:
LOAD PERIOD AS PV_FORE_PERIOD,
  WEEK AS PV_FORE_WEEK
RESIDENT Calandar;
INNER JOIN (Fore_Calandar)
LOAD PV_FORE_WEEK
RESIDENT Planning_View;

Max_Plan_Calandar:
LOAD PV_PLAN_PERIOD,
MAX(PV_PLAN_WEEK) AS PV_PLAN_WEEK
RESIDENT Plan_Calandar
GROUP BY PV_PLAN_PERIOD;

Max_Fore_Calandar:
LOAD PV_FORE_PERIOD,
MAX(PV_FORE_WEEK) AS PV_FORE_WEEK
RESIDENT Fore_Calandar
GROUP BY PV_FORE_PERIOD;

Max_Data:
NOCONCATENATE
LOAD PV_PLAN_WEEK,
  PV_FORE_WEEK,
  ITEMDEMAND
RESIDENT Planning_View;
INNER JOIN (Max_Data)
LOAD PV_PLAN_PERIOD,
  PV_PLAN_WEEK
RESIDENT Max_Plan_Calandar;

//TABLE NOT FOUND ERROR HERE

INNER JOIN (Max_Data)
LOAD PV_FORE_PERIOD,
  PV_FORE_WEEK
RESIDENT Max_Fore_Calandar;

//TABLE NOT FOUND ERROR HERE

DROP TABLE Plan_Calandar;
DROP TABLE Fore_Calandar;
DROP TABLE Max_Plan_Calandar;
DROP TABLE Max_Fore_Calandar;


-br

Arif

Community Browser