When using solidDB^® Transparent Connectivity, the solidDB^® ODBC or JDBC driver hides the existence of two HSB servers from the application. Transparent Connectivity also offers transparent load balancing between the primary and secondary servers.

The driver offers 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 Secondary. This connection will be set to the event wait mode, where it is ready to receive HSB state change events. Those events are the primary source of information about failovers and switchovers that the driver will use. In some cases (such as the Primary Alone operation), the standby connection will be missing, but the driver will try to enact it whenever possible.

The standby connection is handled totally transparently to the application. Also, any occurrence of a connection switch, that is, changing the mapping of the TC Connection to an internal active connection, will be notified to the application by way of a special error code.

Important: solidDB^® tools, such as solidDB^® SQL Editor (solsql), do not support the TC connection.