Limitations
-
PDS only synchronizes in one direction: from the source database to Patterns.
-
PDS has limited throughput, typically a few thousand records per second. Loading an excessive volume of records can take considerable time.
-
PDS has the tradeoff of latency versus resource-consumption typical of polling applications.
-
PDS commands operate independently of each other. A single PDS command performs synchronizations in the order specified by the change_id column in its change-log table. However, when multiple tables are being synchronized using multiple PDS commands, order of synchronization across tables is not guaranteed. Change-log-B can be synced before Change-log-A, even if Change-log-A has earlier changes.