Script seems to pause inbetween - what can be the reason

[datanibbler]

Hi,

the script for my newest app always takes a very long time at a point in the middle:

- The LOAD statement just before that point is a RESIDENT LOAD where a masterdata_table is "pumped up" to generate one record per day <=> but that is already full (conc. the nr. of records) before the break

- The LOAD immediately afterwards is a direct query from the database (a LOAD statement on top of an SQL SELECT)

Can anybody give me an idea of what might be the reason for this?

Thanks a lot!

Best regards,

DataNibbler

[bbi_mba_76]

Hi,

could you see on the task manager ?

There is high CPU usage ?

[datanibbler]

Hi BBI_MBA_74,

I haven't looked yet. I will do so.

[datanibbler]

Nope,

actually, looking at the Task_manager, it seems like there is nothing much happening at all during this break - CPU_load goes down to 6% or so and Memory_usage does not change.

[Peter_Cammaert]

Suggestion for getting additional help:

Reload your document under server control and let it generate a Document log. Take the log from the Distribution Service. That one has timings to the (insert very small fraction prefix here)-second and lets you assign an awful delay to a specific statement. Then post the statement as documented in the log.

BTW how long is that "very long time at a point in the middle" exactly?

Best,

Peter

[bbi_mba_76]

In a similar case I splitted the document into two docs.

But, is the query to the db taking long time?

When qlik break, the db is working?

[#7]

When this happend to me was because the SQL query was actualy slow and had nothing to do with the script reload.

Try to check if your query is slow in some db tool.

cheers,

Juan Pedro

[datanibbler]

Hi juan pedro,

that might well be - that DB table is by far the biggest one in the entire DB. The point where the script "pauses" - for about 1min - is before the SELECT on that table is actually started - so it might be that something about the connection to this particular DB table is troublesome.

@ Peter

That delay is about 1min. I can post the statement just before the break such as it is visible in the progress_window.

According to the log, however, the delay is not BEFORE that SELECT - everything seems fine time-wise till that point - but AFTERWARDS, there is a delay of roughly 1min - after the entire SELECT statement and before another RESIDENT LOAD that's based on it. So it seems like that is really the problem - in which case there's probably nothing much I can do from QlikView's side. I already load just a tiny fraction of that table (WHERE clauses in the SELECT), but the table remains huge.

Thanks a lot!

Best regards,

DataNibbler