Qlik Community

Ask a Question

QlikView App Dev

Discussion Board for collaboration related to QlikView App Development.

Announcements
Join this live chat April 6, 10AM EST - QlikView to Qlik Sense REGISTER
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Left keep and Left join

Hi,

While development, in which cases, should I prefer Left Keep over Left Join, assuming the fact that they produce same result set (though number of tables differ in data model)?

Thanks.

1 Solution

Accepted Solutions
ashfaq_haseeb

Hi,

have a look at attached document

Regards

ASHFAQ

View solution in original post

7 Replies
adiarnon
Creator III
Creator III

mybe this help -

Difference between left Keep vs left Join

left keep

there alot of disccusion about this subject so you can try to search

adi

tresesco
MVP
MVP

If you Join the tables, number of table hoppings would reduce and thus makes the front end performance better. On the other hand perhaps (not tested) Keep would vtake less time during reload in case of a very big data table in join question. Here to mention, in such performance issues ther is one more very effective way called AppyMap could be proven helpful.

ashfaq_haseeb

Hi,

have a look at attached document

Regards

ASHFAQ

View solution in original post

aveeeeeee7en
Specialist III
Specialist III

See this post for clarity:

http://community.qlik.com/thread/39177

Regards

Aviral Nag

engishfaque
Specialist III
Specialist III

Dear qv_learner,

The keep prefix is similar to the Join prefix. Just as the join prefix, it compares the loaded table with an existing named table or the last previously created data table.

But instead of joining the loaded table with an existing table, it has the effect of reducing one or both of the two tables before they are stored in QlikView, based on the intersection of table data.

Reference: QlikView Referene Manual

Kind regards,

Ishfaque ahmed

MayilVahanan

Hi

Its based on your requirement.

If you don't want to join with the parent table but "you need to reduce the data based on the parent table and do some action in your table". In that case, you can prefer keep.

Please refer

Understanding Join, Keep and Concatenate

Thanks & Regards,
Mayil Vahanan R
Not applicable
Author

Thanks for the attachment Ashfaq.