When using solidDB Transparent Connectivity (TC), the solidDB ODBC or JDBC driver hides the existence of two HSB servers from the application and provides transparent load balancing between the primary and secondary servers.

The driver provides a single logical TC connection that is mapped to the internal active connection. In an ideal case, when both primary and secondary servers are running in the active state, the driver also maintains the standby connection, that is, the connection to the secondary server. This connection is set to the event wait mode, where it is ready to receive HSB state change events. Those events provide the main source of information about failovers and switchovers that the driver uses. In some cases (such as when the server is in the PRIMARY ALONE state), the standby connection is missing, but the driver tries to maintain it whenever possible.

The standby connection is handled totally transparently to the application. Also, if there is a connection switch, that is, the mapping of the TC connection is changed to an internal active connection, the application is notified by way of a special error code.