The Connection Pools tab of the Service Properties dialog allows you to specify how long to maintain pooled connections for the Replicator Service, and how often to check the age of pooled connections.
The Connection Time Limit and Pool Inspection Interval settings work together to control how connections are allocated. A connection is closed after it has been inactive for the specified Connection Time Limit. The exact time that a connection will be closed depends on the frequency of the Pool Inspection Interval relative to the Connection Time Limit. If the pooled connections are inspected frequently, unused connections will be closed soon after they reach the Connection Time Limit. For example, if the connections are inspected every 3 minutes in a connection pool with a Connection Time Limit of 30 minutes, an inactive connection will remain open for a maximum of 33 minutes.
Connection Time Limit (minutes) |
Specifies how long the Replicator Service allows each unused, pooled connection to stay open before it is automatically closed. This setting applies to all connection types. To keep all pooled connections open indefinitely, set the Connection Time Limit to 0. Changes to the Connection Time Limit setting takes effect as soon as you click OK. |
Pool Inspection Interval (minutes) |
Specifies how frequently the Replicator Service checks the connection pool for connections that have been inactive for the number of minutes specified for Connection Time Limit. |
Login Timeout (seconds) |
Specifies a timeout limit when initiating an ODBC connection. Default 30 seconds. |
Packet Size (integer) |
Specifies an ODBC packet size when creating a connection. Default 0 (avoid setting the property on a new connection). Example: 32767. |
In situations where ODBC drivers limit the number of connections or the number of users, it is important to close unused connections quickly. If you use such a driver for the maximum number of connections between the Replicator Service and Db2, other processes on the Windows Server will be denied access to the driver as long as the Replicator Service holds those connections open. You may also encounter connection limits when using the SQL Server ODBC driver for connections between the Replicator Service and SQL Server, depending on how you have licensed SQL Server.
If you need to support more users or more connections, see the SQL Server documentation for information about obtaining additional SQL Server licenses. To increase the number of connections allowed by your StarSQL licensing agreement, contact StarQuest Ventures.