Client load balancing helps distribute new connections in your environment so that no one server is overwhelmed with connection requests. When client load balancing is enabled, the order in which primary and alternate database servers are tried is random. For example, let us suppose that client load balancing is enabled as shown in the following illustration:
First, Server B is tried (1). Then, Server C may be tried (2), followed by a connection attempt to Server A (3). In contrast, if client load balancing were not enabled in this scenario, each OpenAccess SDK Server would be tried in sequential order, primary server first, then each alternate OpenAccess SDK server based on its entry order in the alternate servers list.
For details on configuring client load balancing, refer to the OpenAccess SDK Administrator’s Guide.
