Help get this topic noticed by sharing it on Twitter, Facebook, or email.

dynamic replicate call by dbamp when schema changes not using bulkapi nor pkchunk

Is there a way to force dbamp to do a replicate using pkchunck when it does a replicate on the fly after realizing there is a schema change? My issue is dbamp descided to perform a replicate in the missle of the afternoon on a large table because there was a schema change. It took 16 hours and affected out reporting. Is there a setting that forces it to do replicate w/ pkchunk when it does a replicate dynamically?
1 person has
this question