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?
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.
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!