Package Explorer

Execution Modes

Combine 6.0 introduces two package execution modes:

  • Traditional 'Sync' mode.
  • A new 'Async' mode.

'Sync' mode

In this mode scripts are executed synchronously and simultaneously on all databases. I.e. each script execution is started on all databases at the same time, Combine waits until it is completed on all of them, and only then starts to execute the next script.

Figure 142:  Timeline diagram for the 'Sync' mode.

'Async' mode

In this mode scripts are executed on each database without waiting for other databases. Combine starts the next script execution on each database immediately after the previous script is completed. This mode allows Combine to minimize wait time for small databases in case when the corresponding container consists of several databases with significantly different sizes (and hence very different script execution times).

Figure 143:  Timeline diagram for the 'Async' mode.

Set execution mode

'Sync'/'Async' modes are set for a package or any folder inside package.

Figure 144:  Selecting execution mode for a package.

'Mixed' mode

If 'Async' mode is set for some folder (or for the entire package) then all sub-folders despite of their settings are executed in 'Async' mode too. So it is possible to create a series of synchronization points during package execution. To do so user should create a corresponding number of folders and set their modes to 'Async' (the entire package should be in 'Sync' mode). In that case Combine will execute scripts inside each folder asynchronously, but when all scripts inside the folder are completed for one database -- Combine will wait for the other databases before switching to the next folder execution. For example, package has the next structure:

Figure 145:  Package structure example.

Package has 'Sync' mode set, while the folder -- 'Async'. In that case execution diagram will be the next:

Figure 146:  Timeline diagram for a 'Mixed' mode.

© 2001-2017 JNetDirect, Inc. All Rights Reserved.