Contents
Limiting the Number of Connections for Parallel Deployment

Limiting the Number of Connections for Parallel Deployment

When deploying code on target databases in a Container or when executing code packages, Combine connects and deploys code on all target databases in parallel. The number of connections initiated from the Combine machine can therefore be potentially high. In addition, if multiple target databases reside on the same server then Combine will connect to those databases simultaneously. To help you control the number of connections and code execution, you can set two thresholds to limit the maximum number of parallel connections in the options dialog. This dialog can be activated by selecting Tools → Options from the main menu, and the connection limit options are displayed in the Execution Engine section.


    1. Overall Connection Limit: The connection limit reflects the maximum number of parallel connections that Combine will handle over all databases and servers. The default value for this limit is set to 25.

    2. Server Connection Limit: This limit denotes the maximum number of connections that will be launched against a single server. This limit is only useful when multiple target databases reside on the same server. The default value of this limit is set to 2 to ensure that not more than 2 simultaneous connections are opened against any server during code or package execution.




    Figure 76:  The Execution Engine options dialog.






    © 2001-2017 JNetDirect, Inc. All Rights Reserved.