topic Join within database or using a relation in QlikView which method is better? in QlikView

Join within database or using a relation in QlikView which method is better?

amars — Tue, 19 May 2009 13:39:05 GMT

Hi all,

While creating a QlikView file I have taken join in the sql query which increases the no of records & thus size of QlikView File. I can use the join in qlikview by creating aliases, but I don't know which one is better . Any suggestion's on that.

Thanks in advance

Regards

Amar.[:D]

Join within database or using a relation in QlikView which method is better?

Anonymous — Tue, 19 May 2009 20:56:32 GMT

Amar,
First, the number of records (or pretty much any result) depends on what you do, not how you do it. If you join it in SQL or in QV - you get the same.
I asume that you are talking about the link in QV rather than join. In this case you'll get a smaller numbe of records.
As for what is better - it depends on your specific situation.

Join within database or using a relation in QlikView which method is better?

amars — Tue, 19 May 2009 21:28:52 GMT

Thanks Michael,

But my scenerio is like I have data for 1 lakh sales transaction in different currencies , say 10 different currencies. & user want's to see the report's in a single currency that user can select. So I have maintained conversion rates for those currencies. So if I use join's in SQL the effective records will be 1 lakh * 10 = 10 Lakh which is large and makes the file size larger.

But if I will use an alias for the currencies in the conversion table & the transaction table and load it separately , the no of record's will reduce considerably, since I load then separately without SQL join so effective records 1 lakh + 10

so which is the ideal or prefered solution in this case

Thanks in advance.

Regards

Amar

Join within database or using a relation in QlikView which method is better?

Anonymous — Wed, 20 May 2009 00:14:16 GMT

Amar,
WIt depends on your priorities. what is ideal for one client may be not good for another, sorry about that... There is nothing wrong wih the larger file size by itself. Often it may improve the front-end calculations performance. And, over-minimizing the file size may result in a slower front-end performance.