@Patrick, First of all, let me thank you for your amazing reply. I will try to answer all the points referred in your reply as best as I possibly can. It's an ancient version and since I'm used to work with more modern versions of ETL tools, like PowerCenter, CloverETL, among others, it really takes me a step back. This version does not have a CTRL+Z option (to begin with) !!! The job I attached is a regular job with this version. It has a splitter which has a column that serves as a parameter for all the Loops. I cannot nest anymore jobs within a loop, only one. It does have a option for parallelization, which is referenced on the manual, which is "Execute iterations in Parallel" and from the testings I've been doing, it is increasing (a lot) the performance on my most heavy/longer jobs, so thanks a lot for that! My question is if this is a good option to keep on mind and to use for a better performance and for the ETL to take less time to execute. The server is a pretty good machine, with a lot of cores (32 i think), so running one job per processor, as indicated in the manual, is not a bad idea. Another question I have is: - Is it better to use the Execute iterations in Parallel only, or to use the "Enable parallel processing macros" in the Job Property (within the loop) ? Or is it better to use both ? Regarding the scheduler, we only have Control-M which runs the SH, which call SAS Jobs in a specific order. Best regards and thanks!!
... View more
