Best practices for High-speed Apply Engine

We recommend that you review best practices for High-speed Apply Engine product before implementing a product feature or incorporating apply processing into your operational workflows.

Set up apply processing to avoid rework

Establish a consistent approach for creating apply requests and configuration files early in your implementation. Use standard naming conventions for apply requests, configuration files, and input sources. This reduces rework, improves readability, and simplifies troubleshooting and maintenance over time.

Organize input sources for clarity and control

Organize SQL statements and logical log files by purpose, such as migration, recovery, or ongoing change apply. Avoid combining unrelated changes in a single apply request. This improves traceability, simplifies error resolution, and makes restart processing more predictable.

Plan apply runs for recovery and availability

Enable restart processing and ensure that restart tables are created and maintained in the target database. This allows apply requests to resume from the point of failure and helps minimize downtime during recovery or high‑volume apply operations.

Use environment-specific configurations

Create separate configuration files for different environments, such as development, test, and production. Environment-specific configurations help prevent accidental use of incorrect parameters and support safer transitions between environments.

Tune parallel processing carefully

Increase the number of apply agents gradually when enabling multi‑threaded runs. Monitor performance and database resource usage to ensure that parallel processing improves throughput without overloading the target system.

Define conflict resolution rules in advance

Identify expected SQL return codes and database messages before running apply requests and define conflict resolution rules for them. Predefined rules ensure predictable behavior during runs and reduce manual intervention when conflicts occur.

Monitor and review apply results

Review job output, messages, and logs after each apply request. Monitoring run results helps identify performance bottlenecks, detect recurring conflicts, and verify that database changes are applied as expected.