An operative database can only commit two engines to Qlik Replicate (or initial loads at any given time. How should the task settings be modified?

To manage the load on a source database during an initial load, Qlik Replicate provides a specific setting to control concurrency. The "Maximum number of tables to load in parallel" option, located within the task's "Full Load Settings" (specifically on the Tuning tab), dictates how many concurrent processes, or "engines," Replicate will use. By default, this is set to five. To comply with the operative database's limitation of two concurrent engines, this setting must be modified to '2'. This ensures that Replicate does not overwhelm the source system, allowing the initial load to proceed without causing performance degradation or connection failures on the source.

A. "Apply Change Processing Tuning" settings relate to the ongoing Change Data Capture (CDC) phase, not the initial Full Load phase specified in the question.

B. This statement is factually incorrect. By default, Qlik Replicate loads multiple tables (typically five) in parallel to optimize the speed of the Full Load.

D. While the setting is in a "Tuning" sub-section, the primary configuration area is "Full Load Settings". Option C provides a more accurate high-level description of the required action.

1. Qlik Replicate User Guide (May 2023), Section: Task settings > Full Load settings > Tuning tab. The documentation states: "Maximum number of tables to load in parallel: The maximum number of tables that Qlik Replicate can load in parallel from the source database. The default is 5... You may want to decrease this value... if the source system is overloaded." This directly confirms that limiting the number of parallel table loads is the correct method to manage source system constraints. (Accessed via Qlik Help Portal).