Replication scheduling

What is replication scheduling?

An integration’s replication schedule controls the frequency (how often) or the time (when) that replication jobs should start. It is managing the extraction phase of the replication itself.

Now when you are creating a database integration, you can tell SageData when and how often the data replication/extraction should happen. There are few things to keep in mind when creating the replication schedule:

• When defining the replication schedule, you can only the starting time of the replication job
• If an error occurs during the extraction, it will end the current replication job
• Next replication jobs will be skipped, if one replication job is already in progress (one replication job at a time)
• If you have selected multiple tables for your integration, the scheduling will apply to all of them

Replication scheduling methods

SageData is offering few methods for creating your replication schedule:

• Sync historical data
• Replication Frequency
• Replication frequency and anchor time
• Scheduling using cron expressions

Historical data

For historical data you can either use the integrations default or define exact time period (start and end date) for your replication.

Default

Specific

Replication frequency

This method allows you to define how often should SageData run the replication job for integration, based on intervals of 30 minutes, one hour, six hours, 12 hours, and 24 hours.

Here the start times will depend on the start time and duration of the previous job.

Replication frequency and anchor time

This method is a combination between replication frequency and anchor time. The Anchor appoints the start times of replication jobs (to a time selected from the drop-down), and in combination with the Replication Frequency, creates the replication schedule. For example: Run a replication job every 1 hours, starting at 6:30 UTC

Scheduling using cron expressions

This method will allow you to define very specific start times for data extraction. A cron expression is a combination of 6 values that tell SageData when to run the replication. You can select the exact times, days of the week, or even days of the month. For example cron(0 12 * * ? *) runs the rule every day at 12:00pm UTC+0.

You can use the following values for each field:

*Wildcards:

• The , (comma) wildcard includes additional values. In the Month field, JAN,FEB,MAR includes January, February, and March.
• The – (dash) wildcard specifies ranges. In the Day field, 1-15 includes days 1 through 15 of the specified month.
• The * (asterisk) wildcard includes all values in the field. In the Hours field, * includes every hour. You can’t use * in both the Day-of-month and Day-of-week fields. If you use it in one, you must use ? in the other.
• The / (slash) wildcard specifies increments. In the Minutes field, you could enter 1/10 to specify every tenth minute, starting from the first minute of the hour (for example, the 11th, 21st, and 31st minute, and so on).
• The ? (question mark) wildcard specifies any. In the Day-of-month field you could enter 7 and if any day of the week was acceptable, you could enter ? in the Day-of-week field.
• The L wildcard in the Day-of-month or Day-of-week fields specifies the last day of the month or week.
• The W wildcard in the Day-of-month field specifies a weekday. In the Day-of-month field, 3W specifies the weekday closest to the third day of the month.
• The # wildcard in the Day-of-week field specifies a certain instance of the specified day of the week within a month. For example, 3#2 would be the second Tuesday of the month: the 3 refers to Tuesday because it is the third day of each week, and the 2 refers to the second day of that type within the month.