Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Concatenation created table "by resident" to the other table

I create table Segmenty by resident other table Sales. I had some if statemnet so i had to create new table. Now i had to concatenate other xls file to table Sales. To this while everything is OK. But i need to change one field from thiz xls to field from table Segmenty - this one wchich i has changed. To this i know only way. I should cocncatenate this new table Segmenty to table Sales. But when i try to do this i've got alert out of virtual memory. I get notice from IT that more virtual memory i wouldn't have on QV server.

Is this any way to do this. Please help. I have no idea

3 Replies
Not applicable
Author

Are you sure that the concatenate is correct? I suspect that it is being created as a seperate table and that the synthetic key being created is what is using up the memory.

Regards,

Gordon

Not applicable
Author

Well i'm not sure. But i can't check this via my file because it's not working.

My code


Segment:
load
[Client number],
[BU],
[Factory],
[Sales person (Client)],
if([Factory]='NAM', 'FIRE',if(([BU]='FIRE' and [Factory]<>'NAM'), 'PROJEKTY',
if(([Client number]='170013' and
[Factory]='PRU'), 'PROJEKTY',[BU]))) as [Business Unit],

if(([Client number]='170013' and [Factory]='PRU'), 'Krzysztof Cudniewicz',
[Sales person (Client)]) as [Handlowiec]
resident Sales;

Left join (Sales)
load
[Client number],
[Handlowiec] as [DTH],
[Factory],
[Business Unit] as [FinalSeg]
resident Segment;


Not applicable
Author

Ahh! Teminology - I though you meant 'concatenate load' rather than 'join'

Unless you are dropping 'Sales' you will end up with synthetic keys - you code doesnt show the structure of Sales but there will be several common fields between it and 'Segment' . The left join (to 'Sales' not 'Segment' right?) will also be expensive as there are multiple matching fields too.

You may need to think about creating a key field (perhaps using autonumberhash128 or a key field table)

Regards,

Gordon