Joins vs Qliview Association in Qlikview

[#1]

Hi,

I want to understand concepts related to joins and qlikview association:

Why do we go for joining two tables using 'Join' clause , when  we can  just load 2 different tables and let qlikview create the join itself?

Please answer me scenarios where we find each on of them useful.

Thanks,
Sam

[#2]

Hi,

I think if you let qlikview to create joins it will create join in run time after loading the datas in RAM hence it reduces the performance of the report so its better to use join clause in script.

Regards,

Dilipkumar B.S

[#3]

see below

Joins and Lookups

http://community.qlik.com/blogs/qlikviewdesignblog/2012/09/12/to-join-or-not-to-join

[Gabriel]

Hi,

When you import 2 or more tables with same fields name, QV create associate. That is 2 fields with same  name from 2 or more different tables.Associate is just a way for QV saying this two fields are related.

When you import 2 or more tables which has more than 2 fields with same name,QV create something called Synthetic Key. Synthetic key is not good for performance and therefore QV developer use JOIN or CONCATENATE to elimibate synthetic key. This  is not the only reason why developers use JOIN & CONCATENATE but is a reason.

I suggest you read more.

Hope this is helpful.

Best Regards,

Gabriel