Batch push data

Dawid Kaczmarek Updated by Dawid Kaczmarek

Click: Global data management -> Periodic -> Batch push data.

Commit size decides how many records should be updated before the they are committed. There are 3 different approaches for this parameter, that you can benefit from:

Commit size decides how many records should be updated before the they are committed. There are 3 different approaches for this parameter, that you can benefit from:

  • 0 - all of the records will be pushed in one transaction - this is recommended for deployments, where customer wants to make sure to have everything synchronized only in case when there is no error with any record. Safest possible setting but also can be a performance issue (having a one big transaction can degrade SQL DB performance)
  • 1 - every record will be synchronized separately, recommended only when facing issues with data synchronization. Having everything divided in small transactions causes slow performance because of big transaction overhead, but will synchronize data if other records are failing.
  • 2 or greater, recommended 1000 - records are divided between many transactions, best possible performance, recommended in stable environments with no synchronization issues. This value can be adjusted to achieve better results.

By pressing the Filter button, it is possible to limit the number of records that will be pushed by the batch job. Filtering is a standard inquiry.

If the Data table name field name is left blank in the batch inquiry, it is recommended to use the Sequence field on the Management form to set up the correct sequence of tables to push. For more detailed description see 4.1.1 Usage of the Sequence field.

If the Data table name field name is left blank in the batch inquiry, it is recommended to use the Sequence field on the Management form to set up the correct sequence of tables to push. For more detailed description see 4.1.1 Usage of the Sequence field.

The Batch push data job will be initiated only for the data tables in Cepheo GDM, which has records setup with the following conditions on the Selection form:

  • Batch in the Push method field

How did we do?

Batch push data - multi-threaded

Contact