topic How To Skip JOIN in QlikView

How To Skip JOIN

Fri, 06 May 2011 19:51:21 GMT

Hello QlikView Community Experts,

I heard the best practice for reloading data is to FIRST run the query and STORE to QVD files; and SECOND, to reload referencing the QVD.

However, in my FIRST process, I notice that QVD is created, however, it is trying to JOIN "sync" afterwards, which is taking longer than I wanted to be. Is there a way to SKIP the JOIN portion, since the join should be done in my SECOND process. FIRST process is simply creating QVD, and JOIN "sync" should really be done in the SECOND process.

Your help is appreciated!

How To Skip JOIN

johnw — Fri, 06 May 2011 20:04:20 GMT

Are you doing this all in a single script?

One of the main reasons for QVDs is to read the database once, then use the data anywhere, in any QlikView. So you would typically have a separate QVW to create the QVD(s). Then the actual user application QVW(s) would read only from the QVD(s).

Now you could create a QVD from a user application QVW. But if you do, there is no reason to load from that QVD in that application. The table and all its data is already resident, so there's no reason to load it again. If you DO load it again, now you have two copies of the data, which QlikView will try to join together into one table. You don't want two copies of the data.

I could, of course, be totally misunderstanding the problem.

How To Skip JOIN

Fri, 06 May 2011 20:04:37 GMT

Hi, could you post a script example?

How To Skip JOIN

Fri, 06 May 2011 21:35:59 GMT

I'm having problem with the FIRST process (creating the QVD). This QVW has NO reports, simply creating QVDs.

The load script creates 8-10 QVDs. The issue here is that I do not want them to JOIN after they are created.

Main Question:

Is there a way for the reload process to determine whether to JOIN or not to JOIN??

I want the JOIN to occur during end user QVW report reload process (SECOND Process).

Let me know if my question is still not clear.

Cheers.

Below is one of the 10 QVDs in the FIRST process.

DailySC:

SQL SELECT Timespan,

MaxDate,

YrNm,

POS,

Channel,

SubChannel,

Measures, Metrics = CASE Metrics

WHEN 'GP' THEN 'GP(wo ICM) '

WHEN 'Spend' THEN 'Spend(wo ICM)'

WHEN 'CM' THEN 'CM(wo ICM)'

END

FROM “Scorecard_SC"

where channel in('OLA','DPS wo TAAP','TAAP') and POS <>'All POS' and Metrics in('GP','Spend','CM');

Store DailySC into WoICMDailySC.qvd;

How To Skip JOIN

rbecher — Fri, 06 May 2011 21:46:28 GMT

If I understand you right I would suggest to drop every table after the STORE in the first QVW process.

- Ralf

How To Skip JOIN

Fri, 06 May 2011 21:48:00 GMT

IF all tables that you're loading have the same fields they'll automatically JOIN, so after you've stored one, make sure you drop it before loading the next.

How To Skip JOIN

Fri, 06 May 2011 22:23:19 GMT

Thank you Ralf & Carlos. Drop Table works like a charm!!!