Qlik Community

Ask a Question

App Development

Discussion board where members can learn more about Qlik Sense App Development and Usage.

Announcements
April 22, 2PM EST: Learn about GeoOperations in Qlik Sense SaaS READ MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
subramani_r
Contributor II
Contributor II

Force join Vs Association, in terms of User experience to filter values which is faster?

Scenario 1

Table1:

LOAD *

CUSTOMERID,

NAME

FROM ....

Table2:

LOAD *

CUSTOMERID,

Address

FROM ....

 

 

Scenario: 2

Table1:

LOAD *

CUSTOMERID,

NAME

FROM ....

Left join ([Table1])

LOAD *

CUSTOMERID,

Address

FROM ....

 

 

Question: Between the two scenarios, which will yield faster results when filtering on the front end?

Note:

1)The above is just an illustrative example. However, the model I am working with has a lot of columns and rows in multiple fragments of the script.

2) The load time is definitely faster in the 1st case, as its an independent load. However, I want to confirm if the 1st will take more time to load results on dimension intensive charts (such as Sankey, network map etc) as the data between the columns is associated but is not in the same table.

 

Please let me know in case you need any additional information

Labels (1)
1 Solution

Accepted Solutions
PrashantSangle

Single table always works faster.

Great dreamer's dreams never fulfilled, they are always transcended.

View solution in original post

2 Replies
PrashantSangle

Single table always works faster.

Great dreamer's dreams never fulfilled, they are always transcended.

View solution in original post

subramani_r
Contributor II
Contributor II
Author

Thanks a lot 🙂