Scheduled actions can be executed by ETL Designer or by Execution Agent
Actions are Packages, Transformations, Block Transformations, Import Scripts and SQL Scripts.
Be default scheduler execution is disabled.
To enable scheduler:
The second option allows disabling execution remotely using SQL or Management Console
Execute Actions in separate thread
Prevents user interface from freezing, this option decreases performance
Another way to execute actions is by using the agent. The agent is a Windows service that runs continuously in the background, automatically executing actions without user interaction.
To enable agent execution:
The timeout is approximate. Once the timeout is reached, the current action will terminate or stop executing, and no further actions will be performed. This option is only applicable when using the agent.
Execute One Action at the time
Disables parallel execution so only one action is executed at the time. This option only works with the agent.
To avoid access issues with access right we always recommend using the actual user to run it.
Use UNC path for logging.
When execution is enabled, two processes run continuously. The first process checks the schedule, and if there is an item to execute, it adds a record to the queue. The second process monitors the queue, and if it is not empty, it executes the action.
After a record is added to the queue, the scheduler calculates the next execution time.
All scheduling is based on the current time. For example, if the current time is 16:00 and an action is scheduled for 15:00, it will be set for the next day. If an action is scheduled for 17:00, it will occur today.
Multiple instances of our ETL software can connect to the same repository. The options above provide the user with ultimate flexibility in ETL process execution, allowing full control over what actions are performed and where they are executed.
For more technologies supported by our ETL Software see Advanced ETL Processor Versions
Confused? Ask question on our ETL Forum