Question:
Hi everybody,
we have a large data load from an ODS to other ODS. The ODS data receiver has an start routine which makes calculations.
We make this data load by scheduling a job, but we find that not every process is executed in background.
Because of the start routine is executed in a dialog process, a time-out dump occurs.
There are two possible solutions:
- Increase the time-out parameter. This is the easy way but we donīt want to do this.
- Execute the routine in background.
The question is:
Is there any customizing option which allow us executing the routine in background?
Thanks in advance.
Answer:
a third option might be to look at the code that you are executing in your start routine and see if it can be improved for performance.
If the code is bad from a performance point of view, then no matter how much you extend the time-out limit then you will still be only fixing a sypmtom and you could be facing the same problem again in the future.
Answer:
The code is optimized, this is not the right option.
I'd like to ask data package size about.
Is the start routine executed once per data package in a different process?
If this was true, we could work out this problem by reducing the data package size.
Thanks in advance.
Answer:
A start routine is accessed once per actual DataPackage (and thus not once per InfoPackage - unless you program an easy workaround).
Are you really sure the code is performant enough?
To answer your original question: don't think so!