in reply to SQL execution engine - best approach?

If all the actions are in different scripts and these scripts are "called" by some marshalling application, it seems to me that this will involve numerous and repetitive starting of a Perl interpreter, loading a single script, running it and breaking it all down again, only to start all over again with the next script. This seems wasteful of CPU cycles and memory.

One refactoring approach could be to gather all these scripts in one module (that shouldn't be too difficult provided all these modules run under the strict pragma: you could then put each script's main code into a separate subroutine and probably factor out some common code between the scripts in basic/general "servicing" subroutines.

Then your Delphi code just has to start one main script which would perform all the actions of the job within the same invocation of the Perl interpreter. That should be more efficient.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James