Skip to content
Guide

Search the Guide

Enter a query to search the Guide.

Íslenska
Menu
On this page

Automation

The automation page displays and manages job queue entries that automate SQL Connector data transfers. To open the page you can search for "SQL Connector Automation".

Automation

Columns

ColumnDescription
DescriptionJob description (click to open the standard job queue entry card)
Sync TypeParameter strings that control the behavior of the run (see details below)
StatusCurrent status with color codes: Ready (green), On Hold (gray), In Progress (amber), Error (red)
Recurring jobWhether this is a recurring job
Minutes Between RunsInterval between runs
Earliest Start Date/TimeWhen the job may first run
Last Ready StateWhen the job was last set to Ready status
Run on Mondays, Run on Tuesdays, Run on Wednesdays, Run on Thursdays, Run on Fridays, Run on Saturdays, Run on SundaysWeekday checkboxes

Actions

Management

ActionDescription
New Incremental Sync JobCreates a new recurring job queue entry for incremental synchronization with a default 10-minute interval. The default Sync Type is PROCESSCHANGES SENDCOMMANDS. Created on hold.
Set ReadyActivates selected jobs so they will be picked up for execution. Supports multi-select.
Set On HoldPauses selected jobs. Supports multi-select.
Open Job Queue EntryOpens the standard BC job queue entry card for more detailed settings.
DeleteDeletes selected job queue entries after confirmation. If a job is in progress, it is first put on hold before deletion. Supports multi-select.

Processing

ActionDescription
Run NowExecutes the selected job in the foreground.
RefreshUpdates the list to show current statuses.

Sync Type (parameter string)

The Sync Type column (Parameter String on the job queue entry card) controls which steps the run performs. Multiple strings can be combined, e.g. having a job that includes all or some parameter strings.

Parameter stringDescription
PROCESSCHANGESScans active tables and generates data packages (INSERT/UPDATE/DELETE) in the processing log
SENDCOMMANDSSends all pending data packages to configured servers
SKIPCLEANUPSkips automatic cleanup of old processing log and deletion log entries

Common Combinations

CombinationUsage
PROCESSCHANGES SENDCOMMANDSChange processing and dispatch in the same job (default)
PROCESSCHANGES SENDCOMMANDS SKIPCLEANUPChange processing and dispatch in the same job without cleanup
PROCESSCHANGESOnly process changes into data packages
SENDCOMMANDSOnly send data packages that are already pending

Note

Cleanup runs automatically

If SKIPCLEANUP is not specified, old processing log and deletion log entries are automatically cleaned up according to server retention settings.

What happens during a run

When a job queue entry runs, the following steps occur in sequence (if the parameter string contains the corresponding values):

  1. (PROCESSCHANGES) All active tables are scanned for records changed since the last bookmark
  2. (PROCESSCHANGES) External data store commands are generated (INSERT/UPDATE for changes, DELETE for deletions)
  3. (PROCESSCHANGES) Data packages are stored in the processing log
  4. (PROCESSCHANGES) The run saves the packages to ensure they are not rolled back if an error occurs
  5. (SENDCOMMANDS) All pending data packages are sent according to configured servers
  6. (not SKIPCLEANUP) Old processing and deletion log entries are cleaned up according to retention settings