Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

How to create nested inner join in Qlikview?

Hi,

.

someone have an example about how to create  nested inne join in qlikview?

Regards

1 Solution

Accepted Solutions
Peter_Cammaert
Partner - Champion III
Partner - Champion III

Nested JOINs are a SQL feature and do not exist in QlikView script if you don't specify them in SQL (you can use SQL straightaway however). In QlikView script, all JOINS are sequential, even the ones attached to simple LOADs (IMHO). First the LOAD, then the JOIN.

Note that in theory this isn't much different from what an RDBMS does. A nested JOIN (or SELECT) is just a way of specifying complex operations in a not-too-complex-or-talkative-way. But of course the optimizer may still rearrange the actual execution code into something entirely different.

View solution in original post

4 Replies
Chanty4u
MVP
MVP

hi,

Re: qlikview join vs sql joins

Hope this helps u

Thanks

Suresh

jagan
Luminary Alumni
Luminary Alumni

Hi,

What do you mean by Nested Inner join? Can you attach some sample data and your expected result? 

Inner Join Syntax:

Data:

LOAD

*

FROM DataSource1;

INNER JOIN (Data)

LOAD

*

FROM DataSource2;

Regards,

Jagan.

Anonymous
Not applicable
Author

Yea, its possible. You can do nested joins like this:

Table1:

Load *,

ID1

From Table1;

inner join(Table1)

Table2:

Load *,

ID1,

ID2

from Table2;

inner join

Table3:

Load *,

ID2

from Table3;

In this scenario, first Table1 & Table2 will be joined based on ID1 key and then Table3 would be joined Table2 based on ID2 which is already joined to Table1.

After all these joins you will be getting final table i.e Table1.

Hope this will help!!

Peter_Cammaert
Partner - Champion III
Partner - Champion III

Nested JOINs are a SQL feature and do not exist in QlikView script if you don't specify them in SQL (you can use SQL straightaway however). In QlikView script, all JOINS are sequential, even the ones attached to simple LOADs (IMHO). First the LOAD, then the JOIN.

Note that in theory this isn't much different from what an RDBMS does. A nested JOIN (or SELECT) is just a way of specifying complex operations in a not-too-complex-or-talkative-way. But of course the optimizer may still rearrange the actual execution code into something entirely different.