Hi Tushar, thank you for this feature request. However, we're still struggling to understand the real problem. Do you have an example where adding hvr_op creates a bottleneck?

Best regard,

Edwin

Hi Edwin

We have a open case with support of slow capture and many previous occasion / cases  it was told that hvr_op is a slow operation as its process 1 record at a time to fulfil condition apply like {hvr_op} != 0 means do not replicate delete.

So HVR process record by record to validate condition cause slow capture and result in log full in sybase case.

If this can be done at integrate side, its still be a record by record process and latency move from Source to Target but will not impact source server. And for HVR processing Router files is definitely a faster way compare to reading from an end points.

Hi Tushar, ok, the capture restriction is too slow. We will investigate options for this.

Best regards,

Edwin

Hi Tushar,

Our improvement would be to add a Capture/NoDelete option to HVR. That should have minimal impact on the source.

Would that work?

Edwin